Triple
T27341649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ik Kil cenote |
E684118
|
entity |
| Predicate | hasManagedAccess |
P40308
|
FINISHED |
| Object | entrance fee required |
—
|
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: entrance fee required | Statement: [Ik Kil cenote, hasManagedAccess, entrance fee required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasManagedAccess Context triple: [Ik Kil cenote, hasManagedAccess, entrance fee required]
-
A.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
B.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
C.
accessManagedBy
chosen
Indicates that control over access to a resource or system is administered or governed by a specified managing entity.
-
D.
isManaged
Indicates that one entity exercises supervisory or administrative control over another entity.
-
E.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
- 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_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
Created at: April 27, 2026, 11:43 a.m.