Triple
T21528259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andaman Trunk Road |
E531154
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Rangat |
—
|
NE NERFINISHED |
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: Rangat | Statement: [Andaman Trunk Road, connects, Rangat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rangat Context triple: [Andaman Trunk Road, connects, Rangat]
-
A.
Rangat
chosen
Rangat is a coastal town and administrative hub located on Middle Andaman Island in the Andaman and Nicobar Islands, India.
-
B.
Ragau
Ragau is a biblical name appearing in some translations as a variant of the place or figure known as Rages.
-
C.
Rangloi
Rangloi is a regional dialect of the Kumaoni language spoken in parts of the Indian Himalayan region.
-
D.
Ranongga
Ranongga is an island in the Western Province of the Solomon Islands, known for its traditional villages, coral reefs, and subsistence farming communities.
-
E.
Narungga
Narungga are an Aboriginal Australian people and language group traditionally associated with the Yorke Peninsula in South Australia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee8852e68c8190a5341c9f75081382 |
completed | April 26, 2026, 9:49 p.m. |
Created at: April 16, 2026, 6:26 p.m.