Triple
T23516593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zonal railways of Indian Railways |
E574384
|
entity |
| Predicate | typicalSubUnit |
P112029
|
FINISHED |
| Object | railway division |
—
|
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: railway division | Statement: [Zonal railways of Indian Railways, typicalSubUnit, railway division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSubUnit Context triple: [Zonal railways of Indian Railways, typicalSubUnit, railway division]
-
A.
typicalSubunitOf
chosen
Indicates that something is a standard or commonly occurring subcomponent or part of a larger whole.
-
B.
subunitType
Indicates that one entity is a specific kind or classification of subunit within the structure or composition of another entity.
-
C.
subunitOf
Indicates that one entity functions as a component or smaller part within the structure or organization of another, larger entity.
-
D.
subsidiaryUnit
Indicates that one organizational unit functions as a subordinate or dependent division of another, higher-level unit.
-
E.
typicalUnitType
Indicates that one entity is the standard or commonly used unit type associated with measuring or expressing the other entity.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa82a8448190bf7ad56137c5eb94 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.