Triple
T1832391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LEGO Mindstorms EV3 |
E40787
|
entity |
| Predicate | includesMotorType |
P8442
|
FINISHED |
| Object | large servo motor |
—
|
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: large servo motor | Statement: [LEGO Mindstorms EV3, includesMotorType, large servo motor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMotorType Context triple: [LEGO Mindstorms EV3, includesMotorType, large servo motor]
-
A.
electricMotorType
chosen
Indicates the specific kind or category of electric motor associated with an entity.
-
B.
hasMotivePowerType
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
C.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
D.
numberOfMotors
Indicates the quantity of motors associated with or used by an entity.
-
E.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:32 p.m.