Triple
T24196882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU 2003 |
E599858
|
entity |
| Predicate | openingCeremonyBy |
P12834
|
FINISHED |
| Object | Roh Moo-hyun |
—
|
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: Roh Moo-hyun | Statement: [SU 2003, openingCeremonyBy, Roh Moo-hyun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingCeremonyBy Context triple: [SU 2003, openingCeremonyBy, Roh Moo-hyun]
-
A.
hasOpeningCeremony
Indicates that an event or entity includes or is associated with a formal opening ceremony.
-
B.
openingCeremonyHeldBefore
Indicates that the opening ceremony of one event or activity occurs earlier in time than the opening ceremony of another.
-
C.
openingCeremonyDirector
chosen
Indicates the person who is responsible for directing or overseeing the opening ceremony of an event.
-
D.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
E.
closingCeremonyParticipation
Indicates that an entity takes part in the closing ceremony of an event or activity.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e24c103481908ea49dd8e77dee32 |
completed | April 29, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:36 p.m.