Triple
T34240464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Satunsat |
E878448
|
entity |
| Predicate | foundWithinArchaeologicalRegion |
P167717
|
FINISHED |
| Object | Puuc region of Yucatán |
—
|
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: Puuc region of Yucatán | Statement: [Satunsat, foundWithinArchaeologicalRegion, Puuc region of Yucatán]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundWithinArchaeologicalRegion Context triple: [Satunsat, foundWithinArchaeologicalRegion, Puuc region of Yucatán]
-
A.
foundInArchaeologicalZoneCategory
Indicates that an entity is located within or associated with a specific category of archaeological zone.
-
B.
belongsToArchaeologicalZone
chosen
Indicates that something is part of, contained within, or officially assigned to a specific archaeological zone or site.
-
C.
archaeologicalRegions
Indicates a relationship where specific areas are designated or recognized as regions of archaeological interest, activity, or significance.
-
D.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
E.
archaeologyAt
Indicates that an archaeological activity, study, or investigation is conducted at a specific location or site.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 1, 2026, 1:56 a.m.