Triple
T27873655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GE Dash 7 series locomotives |
E704866
|
entity |
| Predicate | configurationVariants |
P161755
|
FINISHED |
| Object | four-axle road switcher |
—
|
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: four-axle road switcher | Statement: [GE Dash 7 series locomotives, configurationVariants, four-axle road switcher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: configurationVariants Context triple: [GE Dash 7 series locomotives, configurationVariants, four-axle road switcher]
-
A.
optimizationVariant
Indicates that one entity is a specific version or alternative form of another entity created for optimization purposes.
-
B.
designVariant
Indicates that one entity is an alternative design or version derived from or related to another entity’s design.
-
C.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
D.
parameterizedVariant
chosen
Indicates that one entity is a specific parameterized form or configuration variant derived from another base entity.
-
E.
returnVariants
Indicates that one entity provides or yields alternative forms, versions, or options of 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 6:25 p.m.