Triple
T15425892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamarajar Port |
E369507
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Ennore |
E369507
|
NE 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: Ennore | Statement: [Kamarajar Port, locatedIn, Ennore]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ennore Context triple: [Kamarajar Port, locatedIn, Ennore]
-
A.
Ennore
chosen
Ennore is a coastal industrial and port suburb in the northern part of Chennai, Tamil Nadu, India.
-
B.
Gentofte
Gentofte is a suburban municipality just north of central Copenhagen in eastern Denmark, known for its affluent residential areas and proximity to the Øresund coast.
-
C.
Hvidovre
Hvidovre is a suburban municipality in the Capital Region of Denmark, located just southwest of central Copenhagen.
-
D.
Valby
Valby is a district in Copenhagen, Denmark, known as an important local transport and residential area within the city.
-
E.
Rødovre
Rødovre is a suburban municipality in the Capital Region of Denmark, located just west of central Copenhagen.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a1849f48190bf898068b2806fae |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03ec1fb288190a3625b8e4f487dd1 |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb593258081909dcaf2b37fd28e63 |
completed | May 9, 2026, 10:30 p.m. |
Created at: April 10, 2026, 3:20 a.m.