Triple
T32976871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kharagpur–Puri line |
E843688
|
entity |
| Predicate | terminusCityType |
P9111
|
FINISHED |
| Object | pilgrimage city |
—
|
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: pilgrimage city | Statement: [Kharagpur–Puri line, terminusCityType, pilgrimage city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusCityType Context triple: [Kharagpur–Puri line, terminusCityType, pilgrimage city]
-
A.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
B.
terminusCityArea
Indicates that a city area serves as the terminal or end-point location for a route, line, or journey.
-
C.
terminusCitySouth
Indicates that something serves as the southern terminus or endpoint located in a particular city.
-
D.
terminusCityWest
Indicates that a route, line, or service has its western terminus located in the specified city.
-
E.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
- 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_69f3494b9fc48190bb61c955ba471275 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:22 a.m.