Triple
T34606829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Coliseum |
E888614
|
entity |
| Predicate | developerOfReplacementComplex |
P114659
|
FINISHED |
| Object | Time Warner |
—
|
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: Time Warner | Statement: [New York Coliseum, developerOfReplacementComplex, Time Warner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerOfReplacementComplex Context triple: [New York Coliseum, developerOfReplacementComplex, Time Warner]
-
A.
replacesComponentOf
Indicates that one entity takes the place of a specific component within another entity, substituting for that component in its role or function.
-
B.
developedAsReplacementFor
chosen
Indicates that one entity was created or designed specifically to take the place of another entity, serving as its successor or substitute.
-
C.
developerRenamedTo
Indicates that a developer previously known by one name is now identified by a new name.
-
D.
masterDeveloper
Indicates that one entity serves as the primary or lead developer responsible for overseeing and controlling the development work of another entity.
-
E.
remakeDeveloper
Indicates that a developer is responsible for creating a new version or adaptation of an existing work (such as a game, app, or software).
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 1, 2026, 2:03 a.m.