Triple
T34674198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Meteor route |
E890453
|
entity |
| Predicate | usesDieselTraction |
P132066
|
FINISHED |
| Object | south of Washington, D.C. |
—
|
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: south of Washington, D.C. | Statement: [Silver Meteor route, usesDieselTraction, south of Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDieselTraction Context triple: [Silver Meteor route, usesDieselTraction, south of Washington, D.C.]
-
A.
usedTractionType
Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
-
B.
drivetrainFeature
Indicates that an entity has a specific characteristic, component, or capability related to its drivetrain system.
-
C.
towingCapability
Indicates the maximum load or object weight that one entity is able to pull or tow.
-
D.
typicalTractionType
chosen
Indicates the usual or most common type of traction mechanism associated with an entity (such as how it is typically powered or driven).
-
E.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72ad38a208190b4bdc828297f86ad |
completed | May 3, 2026, 11 a.m. |
| PD | Predicate disambiguation | batch_69f72a0243988190a43b8ea22457cd30 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 2:05 a.m.