Triple
T97733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IND Division |
E1968
|
entity |
| Predicate | signalSystem |
P522
|
FINISHED |
| Object | fixed-block wayside signals (historically) |
—
|
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: fixed-block wayside signals (historically) | Statement: [IND Division, signalSystem, fixed-block wayside signals (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalSystem Context triple: [IND Division, signalSystem, fixed-block wayside signals (historically)]
-
A.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
B.
roadSystem
Indicates a relationship where multiple roads are organized and connected as part of a larger, integrated transportation network or infrastructure.
-
C.
hasRailSystem
chosen
Indicates that an entity possesses or is served by a rail-based transportation system.
-
D.
notableSystem
Indicates that a system is recognized as significant, prominent, or noteworthy in a particular context or domain.
-
E.
searchesSignalType
Indicates that an entity actively looks for or queries a specific type or category of signal.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebe7b1c8190a6bfbf31dc7c7f07 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.