Triple
T16871348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Outram Island |
E421173
|
entity |
| Predicate | ISO3166-2 |
P189
|
FINISHED |
| Object | IN-AN |
E422136
|
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: IN-AN | Statement: [Outram Island, ISO3166-2, IN-AN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IN-AN Context triple: [Outram Island, ISO3166-2, IN-AN]
-
A.
IN-AN
chosen
IN-AN is the ISO 3166-2 code representing the Andaman and Nicobar Islands union territory of India.
-
B.
Aninri
Aninri is a local government area in southeastern Nigeria known for its rural communities and agricultural activities within Enugu State.
-
C.
INACH
INACH is Chile’s national Antarctic research institute responsible for coordinating and promoting the country’s scientific activities and presence in Antarctica.
-
D.
Aparan
Aparan is a small town in Armenia’s Aragatsotn Province, known for its proximity to Mount Aragats and its historic churches and monuments.
-
E.
Innwa
Innwa is the historical city in Myanmar that served as the capital of several Burmese kingdoms, including the Kingdom of Ava.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f1fe5881909b18438d771814e9 |
completed | April 18, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c2aeb9908190964a9403402186fb |
completed | May 10, 2026, 5:38 p.m. |
Created at: April 10, 2026, 5:29 a.m.