Triple
T9466261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studio 8G |
E228277
|
entity |
| Predicate | hasProductionControlRoom |
P19772
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Studio 8G, hasProductionControlRoom, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductionControlRoom Context triple: [Studio 8G, hasProductionControlRoom, yes]
-
A.
controlRoomFeature
chosen
Indicates that a feature, element, or characteristic is part of, present in, or associated with a control room.
-
B.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
-
C.
controlledChamber
Indicates that an entity has authority over, manages, or directs the operations or decisions of a particular chamber or deliberative body.
-
D.
hasControlTower
Indicates that one entity possesses, hosts, or is equipped with a control tower that manages or oversees its operations.
-
E.
hasQualityControl
Indicates that an entity is subject to processes or measures designed to monitor, verify, and maintain the quality of its outputs or operations.
- 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_69ca846fee388190a6ec273fd644b88b |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fdc08f08190ad17de08d2c2eca2 |
completed | April 1, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:53 p.m.