Triple
T3046717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRT East Side Lines |
E83466
|
entity |
| Predicate | loadingGauge |
P44802
|
FINISHED |
| Object | A Division small-profile |
—
|
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: A Division small-profile | Statement: [IRT East Side Lines, loadingGauge, A Division small-profile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loadingGauge Context triple: [IRT East Side Lines, loadingGauge, A Division small-profile]
-
A.
loadingMechanism
Indicates the method or system by which something is loaded into or onto another object or structure.
-
B.
trackGauge
Indicates the distance between the inner faces of the rails in a railway track system.
-
C.
primaryGauge
Indicates that one gauge is designated as the main or principal measurement instrument among a set of gauges.
-
D.
launchStatus
Indicates the current state or phase of a launch process, such as whether it is planned, in progress, successful, or failed.
-
E.
rollingStockGauge
Indicates that one rolling stock entity is designed to operate on tracks built to a specific track gauge standard.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bad11b48190a5bd01e91a320e14 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f6af3881909f4547967384114c |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.