Triple
T10275280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labná |
E240948
|
entity |
| Predicate | connectedBySacbeTo |
P93072
|
FINISHED |
| Object | Xlapak |
E678805
|
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: Xlapak | Statement: [Labná, connectedBySacbeTo, Xlapak]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Xlapak Context triple: [Labná, connectedBySacbeTo, Xlapak]
-
A.
Xlapak
chosen
Xlapak is a small pre-Columbian Maya archaeological site in Mexico’s Yucatán Peninsula, notable for its well-preserved Puuc-style architecture.
-
B.
Cilapulapu
Cilapulapu is an alternative name for Lapu-Lapu, the Filipino chieftain famed for resisting Spanish colonization and killing Ferdinand Magellan in the Battle of Mactan.
-
C.
Lapinig
Lapinig is a coastal municipality in the province of Northern Samar in the Philippines.
-
D.
Lupao
Lupao is a landlocked agricultural municipality in the province of Nueva Ecija in the Central Luzon region of the Philippines.
-
E.
Lapaha
Lapaha is a historic village in Tonga that served as the former capital and royal seat on the island of Tongatapu.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4dfbfa26c8190b536655d33112ddf |
completed | April 7, 2026, 10:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d75001586c8190a0d4af1ff5588f0e |
completed | April 9, 2026, 7:06 a.m. |
Created at: April 6, 2026, 11:37 a.m.