Triple
T17162466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nidri Beach |
E416514
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Nidri |
E398777
|
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: Nidri | Statement: [Nidri Beach, locatedIn, Nidri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nidri Context triple: [Nidri Beach, locatedIn, Nidri]
-
A.
Nidri
chosen
Nidri is a popular seaside resort town on the eastern coast of the Greek island of Lefkada, known for its scenic bay, nearby islets, and vibrant tourist amenities.
-
B.
Nindra
Nindra is a village and mandal in the Tirupati district of Andhra Pradesh, India.
-
C.
Nadsiannia
Nadsiannia is a historical and ethnographic region of Eastern Europe associated with Ukrainian highlander culture and situated near the Lemko region.
-
D.
Nivy
Nivy is a district of Bratislava, Slovakia, known for its central location, major transport hub, and commercial-residential developments.
-
E.
Nisgha
Nisgha is an alternate name for the Nisga’a language, an indigenous language spoken by the Nisga’a people of northwestern British Columbia, Canada.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f91316108190b0d856d6fa5cd509 |
completed | April 18, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a015fc687788190864fa3922a31184d |
completed | May 11, 2026, 4:49 a.m. |
Created at: April 10, 2026, 5:37 a.m.