Triple
T36158966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4-8-2 Mountain steam locomotives |
E1045817
|
entity |
| Predicate | isNonArticulated |
P52488
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [4-8-2 Mountain steam locomotives, isNonArticulated, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonArticulated Context triple: [4-8-2 Mountain steam locomotives, isNonArticulated, true]
-
A.
testArticulated
chosen
Indicates that an articulated mechanism, structure, or component has been examined or evaluated, typically to verify its movement, function, or performance.
-
B.
doesNotUseRollingStock
Indicates that the subject operates or functions without employing any rolling stock (such as rail vehicles or wheeled transport equipment).
-
C.
isVehicularBridge
Indicates that the subject is a bridge specifically designed and constructed to carry vehicular traffic.
-
D.
isUncrewed
Indicates that an object, vehicle, or mission operates without any human crew physically on board.
-
E.
articulatedWith
Indicates that two parts are connected by a joint or mechanism that allows controlled movement between them.
- 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_69f76e38903c8190a52887620f90aabe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.