Triple
T19971430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyprus at the Winter Olympics |
E480083
|
entity |
| Predicate | openingCeremonyParticipation |
P149
|
FINISHED |
| Object | parade of nations |
—
|
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: parade of nations | Statement: [Cyprus at the Winter Olympics, openingCeremonyParticipation, parade of nations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingCeremonyParticipation Context triple: [Cyprus at the Winter Olympics, openingCeremonyParticipation, parade of nations]
-
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.
participatedInEvent
chosen
Indicates that an entity took part in or was actively involved in a specific event.
-
D.
openingCeremonyDirector
Indicates the person who is responsible for directing or overseeing the opening ceremony of an event.
-
E.
festivalPresence
Indicates that an entity is present at, participates in, or is associated with a particular festival event.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc9694881909a31841702ab9e5f |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.