Triple
T31103060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paddock 11 |
E792724
|
entity |
| Predicate | gateControlledFrom |
P96573
|
FINISHED |
| Object | control room |
—
|
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: control room | Statement: [Paddock 11, gateControlledFrom, control room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gateControlledFrom Context triple: [Paddock 11, gateControlledFrom, control room]
-
A.
endedControlOf
Indicates that one entity has ceased to exercise authority, influence, or governance over another entity or domain.
-
B.
isUnderControlOf
Indicates that one entity is subject to the authority, direction, or governance of another entity.
-
C.
rangeControlledBy
Indicates that the extent or scope of something is regulated, limited, or determined by another entity.
-
D.
canBeControlledFrom
chosen
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
-
E.
isControlledUnder
Indicates that one entity is subject to regulatory, legal, or authoritative control exercised by another entity or governing framework.
- 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_69f224cfd5d881908ec6447bc321cd58 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.