Triple
T25776993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Korean democracy movement |
E649177
|
entity |
| Predicate | strongInRegion |
P32293
|
FINISHED |
| Object | Honam |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Honam | Statement: [South Korean democracy movement, strongInRegion, Honam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strongInRegion Context triple: [South Korean democracy movement, strongInRegion, Honam]
-
A.
regionStrength
Indicates the relative level of influence, power, or dominance that one region holds within a specified context or comparison.
-
B.
strongestSupportRegion
Indicates the region where an entity receives its highest level of support compared to all other regions.
-
C.
strongholdRegion
Indicates that a stronghold (fortified place or base) is located within or associated with a particular geographic region.
-
D.
hasRegionStrongPresence
chosen
Indicates that an entity maintains a significant, influential, or concentrated presence within a specified region.
-
E.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fe5d88548190b070af28fe052ad1 |
completed | May 2, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69f4938b960081909b53c074a3e0c7c2 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 5:35 a.m.