Triple
T28569049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivor: Guatemala |
E722762
|
entity |
| Predicate | mergedTribeName |
P164880
|
FINISHED |
| Object | Xhakúm |
—
|
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: Xhakúm | Statement: [Survivor: Guatemala, mergedTribeName, Xhakúm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedTribeName Context triple: [Survivor: Guatemala, mergedTribeName, Xhakúm]
-
A.
tribeName
chosen
Indicates the name assigned to a tribe in the relationship.
-
B.
tribeNamedAfter
Indicates that a tribe bears a name derived from or given in reference to a particular person, place, group, or concept.
-
C.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
-
D.
hasTribeCommonName
Indicates that two entities are related by the commonly used (vernacular) name of a tribe.
-
E.
introducedTribe
Indicates that one entity caused a tribe to become known, present, or established to another entity or context for the first time.
- F. None of above.
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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6617ba4a88190bfc5c305acb4f93f |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f660f082508190a95a7888ad66cb2e |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 4:08 a.m.