Triple
T17090420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaxhá-Nakúm-Naranjo National Park |
E414708
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Nakúm |
E1247993
|
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: Nakúm | Statement: [Yaxhá-Nakúm-Naranjo National Park, contains, Nakúm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nakúm Context triple: [Yaxhá-Nakúm-Naranjo National Park, contains, Nakúm]
-
A.
Nakum
chosen
Nakum is an ancient Maya archaeological site in northeastern Guatemala, noted for its well-preserved temples and plazas within the Yaxhá-Nakum-Naranjo National Park.
-
B.
Naklua
Naklua is a coastal district in the northern part of Pattaya, Thailand, known for its traditional fishing community, seafood markets, and quieter, more local atmosphere compared to central Pattaya.
-
C.
Nakop
Nakop is a small border settlement in the Northern Cape province of South Africa, located at the frontier with Namibia.
-
D.
Naju
Naju is a historic city in South Korea known for its pear cultivation and location in the southwestern province of South Jeolla.
-
E.
Nacyna
Nacyna is a small river in southern Poland that flows through the city of Rybnik.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbf948d88190a4dd4a0774a8505b |
completed | April 18, 2026, 7:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0139fa0a288190af69201ec88ec3c6 |
completed | May 11, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:35 a.m.