Triple
T29120105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reason |
E737155
|
entity |
| Predicate | centralRobot |
P181233
|
FINISHED |
| Object | QT-1 |
—
|
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: QT-1 | Statement: [Reason, centralRobot, QT-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralRobot Context triple: [Reason, centralRobot, QT-1]
-
A.
centralCommand
Indicates that one entity serves as the primary controlling or coordinating authority over the operations, decisions, or activities of another entity or group.
-
B.
robotType
Indicates the specific category or kind of robot that an entity belongs to.
-
C.
centralWork
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
D.
isFullyRobotic
Indicates that the entity operates entirely through robotic mechanisms without human biological components or manual control.
-
E.
robotControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the actions and behaviors of one or more robots.
- 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
| PDg | Predicate description generation | batch_69f76759b3c48190ad8f1b33596f98c4 |
completed | May 3, 2026, 3:18 p.m. |
Created at: April 28, 2026, 11:25 a.m.