Triple
T35524277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Delhi railway station |
E1026627
|
entity |
| Predicate | isHistoricStation |
P4238
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Old Delhi railway station, isHistoricStation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricStation Context triple: [Old Delhi railway station, isHistoricStation, true]
-
A.
isHistoric
chosen
Indicates that something has significant importance or relevance in history, often due to its age, impact, or role in past events.
-
B.
isOneOfOldestStationsInSystem
Indicates that the station is among the earliest or first-built stations within the entire system.
-
C.
isHistoricFor
Indicates that something has historical significance, relevance, or impact specifically in relation to a given entity or context.
-
D.
isHistoricSee
Indicates that one entity serves or functioned as a historically significant viewing point or place from which another entity is or was seen.
-
E.
isHistoricalName
Indicates that a given name is a former or past designation historically used for an entity.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.