Triple
T38068582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boom Tube |
E950534
|
entity |
| Predicate | controlledByDevice |
P199832
|
FINISHED |
| Object | Mother Box |
—
|
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: Mother Box | Statement: [Boom Tube, controlledByDevice, Mother Box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByDevice Context triple: [Boom Tube, controlledByDevice, Mother Box]
-
A.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
-
B.
controlsDeviceType
Indicates that an entity has authority over or can operate a specific type or category of device.
-
C.
isRemoteControlled
Indicates that an entity is operated or controlled from a distance via a remote device or system.
-
D.
controlDeviceTypical
Indicates that an entity typically operates or manages the functioning of a device.
-
E.
hostControlled
Indicates that one entity is under the control, management, or authority of a host entity.
- F. None of above. chosen
Provenance (4 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff59b33a38819086cc9aa19b81748b |
completed | May 9, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69ff587758f88190a39c2164341dc554 |
completed | May 9, 2026, 3:53 p.m. |
| PDg | Predicate description generation | batch_69ff59b1e2ac8190bb65529e9dbbb178 |
completed | May 9, 2026, 3:58 p.m. |
Created at: May 3, 2026, 4:21 p.m.