Triple
T8131749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weaver rail |
E189867
|
entity |
| Predicate | hasRailWidth |
P81651
|
FINISHED |
| Object | approximately 0.835 inches |
—
|
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: approximately 0.835 inches | Statement: [Weaver rail, hasRailWidth, approximately 0.835 inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRailWidth Context triple: [Weaver rail, hasRailWidth, approximately 0.835 inches]
-
A.
usesRailGauge
Indicates that one entity (typically a railway system or line) operates using the specified rail gauge measurement of the other entity.
-
B.
hasRackRailway
Indicates that one entity possesses or includes a rack railway system connecting locations or operating within its area.
-
C.
hasRailMode
Indicates that an entity is associated with or supports transportation via rail-based modes (such as trains, trams, or subways).
-
D.
hasRailConfiguration
Indicates that an entity is associated with, or characterized by, a particular arrangement or setup of rails.
-
E.
hasRailRoute
Indicates that there exists a rail-based transportation route or connection between the related entities.
- 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_69ca82bcb4848190a9a9d036ad768642 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4c4c2e388190b86854f8b1765e61 |
completed | March 31, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69cb3696379c8190a20965e59ed8f370 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4c496a8c81909aea840248d85d50 |
completed | March 31, 2026, 4:23 a.m. |
Created at: March 30, 2026, 5:34 p.m.