Triple
T9164861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Eastern Railway |
E219924
|
entity |
| Predicate | absorbedIntoDate |
P50534
|
FINISHED |
| Object | 1923 |
—
|
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: 1923 | Statement: [North Eastern Railway, absorbedIntoDate, 1923]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: absorbedIntoDate Context triple: [North Eastern Railway, absorbedIntoDate, 1923]
-
A.
dateAbsorbedApprox
Indicates that one entity was absorbed into another on an approximate or uncertain date, rather than on a precisely known date.
-
B.
incorporatedIntoOnDate
chosen
Indicates that one entity was formally incorporated into or merged with another entity on a specific date.
-
C.
consolidationDate
Indicates the date on which multiple entities, records, or accounts are formally combined into a single consolidated whole.
-
D.
accessionDate
Indicates the date on which an item, record, or entity was formally added to a collection, system, or repository.
-
E.
admissionDate
Indicates the date on which an entity (such as a person, application, or item) is formally admitted, accepted, or entered into a system or institution.
- 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_69ca83e3633c81908688a9fa2306ba99 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccaa2ee64c8190a9a5abafe5d0b086 |
completed | April 1, 2026, 5:16 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:22 p.m.