Triple
T27341634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ik Kil cenote |
E684118
|
entity |
| Predicate | hasUseInPast |
P136896
|
FINISHED |
| Object | ritual site |
—
|
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: ritual site | Statement: [Ik Kil cenote, hasUseInPast, ritual site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUseInPast Context triple: [Ik Kil cenote, hasUseInPast, ritual site]
-
A.
usedInPastFor
chosen
Indicates that one entity was previously utilized for another entity or purpose in the past.
-
B.
usedInPast
Indicates that an entity has been utilized or employed at some point in the past, prior to the current time or context.
-
C.
usedInPastBy
Indicates that an entity was previously utilized or employed by another entity at some time in the past.
-
D.
hasFormerUse
Indicates that something previously served a particular function or role that it no longer has.
-
E.
hasHumanUse
Indicates that something is used, employed, or utilized by humans for a particular purpose or benefit.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 11:43 a.m.