Triple
T36158969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4-8-2 Mountain steam locomotives |
E1045817
|
entity |
| Predicate | hasNumberOfTrailingAxles |
P198932
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [4-8-2 Mountain steam locomotives, hasNumberOfTrailingAxles, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfTrailingAxles Context triple: [4-8-2 Mountain steam locomotives, hasNumberOfTrailingAxles, 1]
-
A.
hasAxleCount
Indicates the number of axles that an object (typically a vehicle or rolling stock) possesses.
-
B.
numberOfAxlesDriven
Indicates the count of axles on a vehicle that are actively powered or driven by the propulsion system.
-
C.
hasSeparateTrailingTruck
Indicates that an entity is accompanied by a distinct, independently attached trailing truck or carriage rather than having it integrated into its main structure.
-
D.
hasAxleConfiguration
Indicates that an entity is associated with a specific arrangement or configuration of its axles.
-
E.
hasTrailingWheelArrangement
Indicates that an entity (typically a vehicle) possesses a specific configuration of wheels located at its rear or trailing end.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_69ff14d4dfc48190bc9fba2384988a98 |
completed | May 9, 2026, 11:04 a.m. |
Created at: May 3, 2026, 4:08 p.m.