Triple
T19450002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fell centre rail system |
E486590
|
entity |
| Predicate | wheelOrientation |
P135190
|
FINISHED |
| Object | horizontal |
—
|
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: horizontal | Statement: [Fell centre rail system, wheelOrientation, horizontal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelOrientation Context triple: [Fell centre rail system, wheelOrientation, horizontal]
-
A.
locationOrientation
chosen
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
-
B.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
C.
rotationSense
Indicates the direction or orientation in which an object or system rotates relative to a defined reference frame.
-
D.
orientationMechanism
Indicates a mechanism or process by which an entity determines, adjusts, or maintains its spatial or directional orientation relative to some reference.
-
E.
spinOrientation
Indicates the relative direction or alignment of an entity’s spin or rotational motion with respect to a chosen reference.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6338caeb48190aeb1d511996984e3 |
completed | April 20, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.