Triple
T37115874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Main Line of Central Railway |
E919115
|
entity |
| Predicate | branchFrom |
P12137
|
FINISHED |
| Object | Kalyan–Kasara line |
—
|
NE NERFINISHED |
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: Kalyan–Kasara line | Statement: [Main Line of Central Railway, branchFrom, Kalyan–Kasara line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchFrom Context triple: [Main Line of Central Railway, branchFrom, Kalyan–Kasara line]
-
A.
branchesFrom
chosen
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
-
B.
branchOrigin
Indicates that one entity is the source or starting point from which another entity branches or diverges.
-
C.
branchLine
Indicates a relationship where one line, route, or path diverges from and is subordinate to a main or primary line.
-
D.
branchPoint
Indicates a point in a process, structure, or path where a single preceding element splits into two or more alternative continuations or options.
-
E.
branchAllocation
Indicates how resources, responsibilities, or items are distributed or assigned across different branches or subdivisions.
- 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_69f76e9c57148190ba789dd059645bb9 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.