Triple
T2233922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MS in Robotic Systems Development |
E49232
|
entity |
| Predicate | hostUnitType |
P13867
|
FINISHED |
| Object | robotics research institute |
—
|
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: robotics research institute | Statement: [MS in Robotic Systems Development, hostUnitType, robotics research institute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostUnitType Context triple: [MS in Robotic Systems Development, hostUnitType, robotics research institute]
-
A.
hostsUnitType
chosen
Indicates that one entity serves as a location or platform that accommodates or contains a specified type of unit.
-
B.
hostsUnit
Indicates that one entity serves as the location or container in which another unit is situated, operates, or is organized.
-
C.
basedUnitType
Indicates that one unit is defined or derived in terms of another underlying (base) unit type.
-
D.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
E.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc0913f1c8190ac9cfeb0f1c84a76 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.