Triple
T4813475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B Division |
E107127
|
entity |
| Predicate | usesLoadingGauge |
P44802
|
FINISHED |
| Object | B Division loading gauge |
—
|
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: B Division loading gauge | Statement: [B Division, usesLoadingGauge, B Division loading gauge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLoadingGauge Context triple: [B Division, usesLoadingGauge, B Division loading gauge]
-
A.
loadingGauge
chosen
Indicates the clearance limits or spatial envelope within which a vehicle or load must fit to safely pass through infrastructure such as tunnels, bridges, or platforms.
-
B.
usesIndicator
Indicates that one entity employs or relies on another entity as an indicator, signal, or metric for assessment, decision-making, or interpretation.
-
C.
loadingMechanism
Indicates the method or system by which something is loaded into or onto another object or structure.
-
D.
primaryGauge
Indicates that one gauge is designated as the main or principal measurement instrument among a set of gauges.
-
E.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
- 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_69bd43f779448190b92885cb70abb6c2 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.