Triple
T37206695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dholpur Railways (portion) |
E922189
|
entity |
| Predicate | operatorAfterIncorporation |
P203837
|
FINISHED |
| Object | Indian Railways |
E100843
|
NE 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: Indian Railways | Statement: [Dholpur Railways (portion), operatorAfterIncorporation, Indian Railways]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorAfterIncorporation Context triple: [Dholpur Railways (portion), operatorAfterIncorporation, Indian Railways]
-
A.
statusBeforeIncorporation
Indicates the legal or organizational status an entity held prior to its formal incorporation.
-
B.
laterIncorporated
Indicates that one entity was formally established, merged, or integrated as a legal or organizational body at a later time than another entity or reference point.
-
C.
incorporationAfter
Indicates that one entity is incorporated or formally established at a later time than another entity.
-
D.
laterIncorporatedInto
Indicates that one entity was subsequently merged into, absorbed by, or formally made part of another entity at a later time.
-
E.
parentCompanyAfterMerger
Indicates that one company is the resulting parent company of another following a merger.
- F. None of above. chosen
Provenance (5 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_69f76ea4849481909b4a3073efb0114c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a021706e21c81909b83e2b4d9c4130c |
completed | May 11, 2026, 5:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a403603b4808190b0ea8cf6c60e0146 |
completed | June 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_6a0216861214819097d2177755bc19d7 |
completed | May 11, 2026, 5:48 p.m. |
| PDg | Predicate description generation | batch_6a02170637bc8190ac89df21358f1624 |
completed | May 11, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:15 p.m.