Triple
T34645645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxchuc |
E889686
|
entity |
| Predicate | usesTraditionalAuthoritySelection |
P191036
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Oxchuc, usesTraditionalAuthoritySelection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTraditionalAuthoritySelection Context triple: [Oxchuc, usesTraditionalAuthoritySelection, yes]
-
A.
usesTraditionalSystem
Indicates that an entity operates according to or relies on a traditional, established system rather than a modern or alternative one.
-
B.
usesTraditionalDecoration
Indicates that an entity employs customary or historically established decorative styles or motifs in its design or presentation.
-
C.
hasTraditionalRights
Indicates that an entity possesses customary or historically established rights or privileges in relation to another entity or resource.
-
D.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
E.
traditionalAuthorityOver
Indicates that one entity holds customary or historically established power, control, or decision-making authority over another entity.
- F. None of above. chosen
Provenance (4 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: May 1, 2026, 2:04 a.m.