Triple
T21622788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheonggyecheon Stream |
E533618
|
entity |
| Predicate | eraOfMajorRestoration |
P59927
|
FINISHED |
| Object | early 2000s |
—
|
LITERAL FINISHED |
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: early 2000s | Statement: [Cheonggyecheon Stream, eraOfMajorRestoration, early 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfMajorRestoration Context triple: [Cheonggyecheon Stream, eraOfMajorRestoration, early 2000s]
-
A.
eraOfMajorConstruction
Indicates the time period during which the primary or most significant phase of construction for an entity took place.
-
B.
significantRestoration
chosen
Indicates that an entity has undergone a major or substantial restoration effort that notably improves or returns it to a previous condition.
-
C.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
D.
restorationEvent
Indicates an event in which something previously altered, damaged, or degraded is returned to a former or improved state.
-
E.
dynastyRestored
Indicates that a previously displaced ruling dynasty has been returned to power or reestablished as the legitimate authority.
- 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bb0c42c8190997fbeb7a764d60e |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:34 p.m.