Triple
T16817485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TVM-300 |
E408790
|
entity |
| Predicate | speedSupervision |
P124968
|
FINISHED |
| Object | on-board computer |
—
|
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: on-board computer | Statement: [TVM-300, speedSupervision, on-board computer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speedSupervision Context triple: [TVM-300, speedSupervision, on-board computer]
-
A.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
-
B.
speed
Indicates the rate at which an entity moves or changes position over time.
-
C.
regulatesSpeedLimitBy
Indicates that one entity determines, controls, or sets the speed limit applicable to another entity or context.
-
D.
speedLimitCharacteristic
Indicates that an entity has a specific speed limit property or constraint associated with it.
-
E.
maxSpeed
Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e30cf48190a61936ba0a49df24 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:23 a.m.