Triple
T5310408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York City Opera |
E119011
|
entity |
| Predicate | presentedWorksIn |
P4490
|
FINISHED |
| Object | English translation |
—
|
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: English translation | Statement: [New York City Opera, presentedWorksIn, English translation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentedWorksIn Context triple: [New York City Opera, presentedWorksIn, English translation]
-
A.
notableWorkPresented
Indicates that a particular notable work was presented, exhibited, or showcased by an entity (such as a person or organization).
-
B.
exhibitsWorkOf
Indicates that one entity displays or presents the creative works produced by another entity.
-
C.
coPresentedWithWorkBy
Indicates that a work is presented together with another specified work, typically within the same event, session, or exhibition.
-
D.
presentedIn
chosen
Indicates that something is shown, displayed, or formally introduced within a particular context, medium, event, or setting.
-
E.
hasExhibitionsAbout
Indicates that one entity organizes or presents exhibitions whose subject matter concerns another entity.
- 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.