Triple
T14547768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubai Opera |
E341331
|
entity |
| Predicate | notableOpeningEvent |
P114888
|
FINISHED |
| Object | Plácido Domingo concert |
—
|
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: Plácido Domingo concert | Statement: [Dubai Opera, notableOpeningEvent, Plácido Domingo concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOpeningEvent Context triple: [Dubai Opera, notableOpeningEvent, Plácido Domingo concert]
-
A.
notableOpening
Indicates that an entity is particularly recognized or distinguished for its opening section, move, scene, or initial part.
-
B.
notableGameEvent
Indicates that a specific game is associated with a significant or noteworthy event in its history or context.
-
C.
game1NotableEvent
Indicates that a specific event is recognized as a notable or significant occurrence within the context of game1.
-
D.
notableSubevent
Indicates that one event is a particularly significant or noteworthy component within a larger, encompassing event.
-
E.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
- F. None of above. chosen
Provenance (4 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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb2ebdf9481909f4d2da1ad31099c |
completed | April 14, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69de610330a48190b558235a14c0dc9f |
completed | April 14, 2026, 3:45 p.m. |
Created at: April 10, 2026, 1:23 a.m.