Triple
T16434046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lion (steam locomotive) |
E399137
|
entity |
| Predicate | hasCylinderPosition |
P95322
|
FINISHED |
| Object | inside cylinders |
—
|
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: inside cylinders | Statement: [Lion (steam locomotive), hasCylinderPosition, inside cylinders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCylinderPosition Context triple: [Lion (steam locomotive), hasCylinderPosition, inside cylinders]
-
A.
cylinderPosition
chosen
Indicates the spatial location or placement of a cylinder relative to a defined reference frame or environment.
-
B.
hasCabPosition
Indicates that an entity has a specific position or placement of a cab relative to its overall structure or configuration.
-
C.
hasTankPosition
Indicates that an entity occupies or is assigned to a specific tank position or location.
-
D.
cylindersBankAngle
Indicates the angle at which the cylinders in an engine are arranged or inclined relative to the engine’s central bank or reference plane.
-
E.
hasCone
Indicates that one entity possesses, is equipped with, or is characterized by a cone or cone-shaped component.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba01a1c8190b5a4700e2364ae63 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.