Triple
T27127540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thanjavur–Nagapattinam line |
E681471
|
entity |
| Predicate | connectsTypeOfPlace |
P184356
|
FINISHED |
| Object | inland cultural hub |
—
|
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: inland cultural hub | Statement: [Thanjavur–Nagapattinam line, connectsTypeOfPlace, inland cultural hub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsTypeOfPlace Context triple: [Thanjavur–Nagapattinam line, connectsTypeOfPlace, inland cultural hub]
-
A.
connectsTypeOfCity
Indicates a relationship where one entity is linked to another as a specific type or category of city.
-
B.
connectsTypeOfAreas
Indicates a relationship where one entity serves as a link or connector between two different types of areas.
-
C.
placeType
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
D.
connectedToPlace
Indicates that one entity has a spatial, functional, or relational link or association with a specific place.
-
E.
connectsCity
Indicates a relationship where one entity serves as a link or route that joins or provides direct access between two cities.
- F. None of above. chosen
Provenance (4 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 27, 2026, 9:02 a.m.