Triple
T4151836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Opera Orchestra |
E89923
|
entity |
| Predicate | performsWorldwide |
P1381
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Metropolitan Opera Orchestra, performsWorldwide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performsWorldwide Context triple: [Metropolitan Opera Orchestra, performsWorldwide, true]
-
A.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
B.
salesWorldwide
Indicates a relationship where an entity’s sales figures or activities are measured, reported, or occur across multiple countries or global markets.
-
C.
operatesInternationally
Indicates that the entity conducts activities or business across national borders in multiple countries.
-
D.
hasWorld
Indicates that an entity possesses, is associated with, or encompasses a particular world or global context.
-
E.
hasGlobalReach
chosen
Indicates that an entity’s influence, operations, or impact extends across multiple countries or worldwide.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.