Triple
T5739901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Railway Budget of India |
E126587
|
entity |
| Predicate | mergeEffectiveYear |
P23631
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Railway Budget of India, mergeEffectiveYear, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergeEffectiveYear Context triple: [Railway Budget of India, mergeEffectiveYear, 2017]
-
A.
mergerYear
Indicates the year in which two or more entities formally merged into a single entity.
-
B.
effectiveYear
chosen
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
C.
mergedBy
Indicates that one entity is combined or integrated into another entity through the action or decision of a specific agent.
-
D.
mergedInto
Indicates that one entity has been combined with and absorbed into another entity, ceasing to exist as a separate unit.
-
E.
renamedYear
Indicates the year in which an entity underwent a renaming or change of name.
- 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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255f302c819094f97b4defeded07 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.