Triple
T29149306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyric Theatre, New York |
E738858
|
entity |
| Predicate | hasInteriorElementsFrom |
P123660
|
FINISHED |
| Object | original Apollo Theatre (1904) |
—
|
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: original Apollo Theatre (1904) | Statement: [Lyric Theatre, New York, hasInteriorElementsFrom, original Apollo Theatre (1904)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorElementsFrom Context triple: [Lyric Theatre, New York, hasInteriorElementsFrom, original Apollo Theatre (1904)]
-
A.
hasInteriorContentType
Indicates that something contains internal material or content of a specified type.
-
B.
hasInteriorItem
chosen
Indicates that one entity contains another entity as an item located within its interior.
-
C.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
D.
hasInteriorBehavior
Indicates that an entity exhibits a particular behavior or set of behaviors within its internal or enclosed space.
-
E.
hasEmptyInterior
Indicates that the interior of an entity is completely hollow or contains no material.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe72dca2f08190beff17de3d2aada6 |
completed | May 8, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69fe70bca8d08190b810e1e616ceac44 |
completed | May 8, 2026, 11:24 p.m. |
Created at: April 28, 2026, 11:41 a.m.