Triple
T24587126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio TC2 |
E608425
|
entity |
| Predicate | hasNeighbouringStudio |
P81924
|
FINISHED |
| Object | Studio TC1 |
—
|
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: Studio TC1 | Statement: [Studio TC2, hasNeighbouringStudio, Studio TC1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighbouringStudio Context triple: [Studio TC2, hasNeighbouringStudio, Studio TC1]
-
A.
hasNeighboringStudios
chosen
Indicates that one studio is located adjacent to or in close proximity to another studio.
-
B.
hasStudiosIn
Indicates that an entity operates or maintains studio facilities located in a specified place or region.
-
C.
hasStudio
Indicates that an entity (such as a film, game, or production) is associated with or produced by a particular studio.
-
D.
hasNeighbouringTheatre
Indicates that one theatre is located close enough to another theatre to be considered its neighbor.
-
E.
ownedStudio
Indicates that one entity possessed ownership or controlling interest in a particular studio.
- 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_69e2c4ce89248190ad99e18f0638dfbb |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a988393c81909f0292e9b35441d2 |
completed | April 30, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f2a6c1f07081908edf0b521767e79b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:29 a.m.