Triple
T37164191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVB-H |
E920750
|
entity |
| Predicate | supportsMobilitySpeed |
P153293
|
FINISHED |
| Object | high-speed mobility |
—
|
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: high-speed mobility | Statement: [DVB-H, supportsMobilitySpeed, high-speed mobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMobilitySpeed Context triple: [DVB-H, supportsMobilitySpeed, high-speed mobility]
-
A.
supportsMobilityFeature
Indicates that an entity provides or enables a mobility-related capability or feature for another entity.
-
B.
supportsMobilityType
Indicates that one entity provides compatibility with, or can function using, a specified type of mobility or movement mode.
-
C.
supportsMobilityBetween
Indicates that one entity enables, facilitates, or allows movement or travel between two or more other entities or locations.
-
D.
hasMobilityConcept
Indicates a relationship where an entity is associated with, or characterized by, a specific concept or model of mobility (e.g., movement, transportation, or locomotion).
-
E.
supportsVelocity
chosen
Indicates that one entity is capable of handling, providing, or being compatible with velocity-related data, behavior, or operations for another entity.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.