Triple
T33236356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaynagar–Janakpur–Bardibas railway line |
E850838
|
entity |
| Predicate | ownerInIndia |
P125603
|
FINISHED |
| Object | Indian Railways |
—
|
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: Indian Railways | Statement: [Jaynagar–Janakpur–Bardibas railway line, ownerInIndia, Indian Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerInIndia Context triple: [Jaynagar–Janakpur–Bardibas railway line, ownerInIndia, Indian Railways]
-
A.
ultimateOwnerOf
Indicates that one entity is the final, controlling owner of another entity, either directly or through one or more intermediate ownership layers.
-
B.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
-
C.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
D.
ownerNationality
Indicates that the owner of an entity has the specified nationality.
-
E.
ownershipBasedIn
chosen
Indicates that an entity’s ownership or controlling stake is primarily located, registered, or based in a particular place or jurisdiction.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:31 a.m.