Triple
T1457086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madras Port |
E31422
|
entity |
| Predicate | navalProximity |
P15652
|
FINISHED |
| Object | near Indian Navy facilities in Chennai |
—
|
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: near Indian Navy facilities in Chennai | Statement: [Madras Port, navalProximity, near Indian Navy facilities in Chennai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalProximity Context triple: [Madras Port, navalProximity, near Indian Navy facilities in Chennai]
-
A.
nearIsland
Indicates that one entity is located close to or in the vicinity of an island.
-
B.
navalAccess
Indicates that one entity has the right or ability to use another entity’s naval facilities, waters, or maritime routes for military or strategic purposes.
-
C.
nearbyStrait
Indicates that one entity is located close to or adjacent to a particular strait.
-
D.
hasNearbyCoast
Indicates that one location is situated close to a coastline or seashore.
-
E.
nearMilitaryInstallation
chosen
Indicates that one entity is located in close physical proximity to a military installation or facility.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c598b30c8190b87207adf608b89a |
completed | March 1, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69a4c47ec5108190b1772237f2e5d90b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.