Triple
T27059721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xcalakoop |
E685000
|
entity |
| Predicate | likelyLanguage |
P94296
|
FINISHED |
| Object | Yucatec Maya |
—
|
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: Yucatec Maya | Statement: [Xcalakoop, likelyLanguage, Yucatec Maya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyLanguage Context triple: [Xcalakoop, likelyLanguage, Yucatec Maya]
-
A.
probableLanguageType
Indicates that something is likely to belong to, be expressed in, or be categorized under a particular language or type of language.
-
B.
possibleLanguage
chosen
Indicates that an entity could plausibly be expressed, interpreted, or communicated in a given language.
-
C.
likelyUse
Indicates that one entity is expected or probable to use, employ, or make use of another entity in a given context.
-
D.
eligibleLanguage
Indicates that a particular language satisfies the required conditions to be considered valid or allowed in a given context.
-
E.
likelySource
Indicates that one entity is considered the probable origin or cause of another entity or event.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622e3ab7081909692e4857e7d7633 |
completed | May 2, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:20 a.m.