Triple
T17840315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TGV |
E445505
|
entity |
| Predicate | recordSpeedCategory |
P129378
|
FINISHED |
| Object | conventional wheeled train speed record |
—
|
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: conventional wheeled train speed record | Statement: [TGV, recordSpeedCategory, conventional wheeled train speed record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordSpeedCategory Context triple: [TGV, recordSpeedCategory, conventional wheeled train speed record]
-
A.
speedClass
Indicates the categorical speed level or range assigned to an entity based on how fast it moves or operates.
-
B.
relativeSpeedCategory
Indicates the categorized comparison of one entity’s speed relative to another (e.g., slower, similar, or faster).
-
C.
raceCategory
Indicates the classification of an entity into a specific race or racial group within a defined categorization system.
-
D.
hasSpeedLimitCategory
Indicates that an entity is associated with a specific category or classification of speed limit.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d2b2ea08190926ec0cf01285833 |
completed | April 19, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e266888190ae976b4b7d5b886f |
completed | April 18, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69e3f022ec448190a9bf191be1c5f570 |
completed | April 18, 2026, 8:57 p.m. |
Created at: April 10, 2026, 10:16 a.m.