Triple
T16951637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Andrés, Petén |
E411192
|
entity |
| Predicate | nearbyArchaeologicalRegion |
P73295
|
FINISHED |
| Object | Maya area |
—
|
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: Maya area | Statement: [San Andrés, Petén, nearbyArchaeologicalRegion, Maya area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyArchaeologicalRegion Context triple: [San Andrés, Petén, nearbyArchaeologicalRegion, Maya area]
-
A.
nearbyArchaeologicalCulture
Indicates that one archaeological culture is geographically close to another archaeological culture.
-
B.
nearAncientRegion
chosen
Indicates that one entity is located close to, or in the immediate vicinity of, a specified ancient geographical region.
-
C.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
D.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
E.
nearbyRockArtSite
Indicates that one entity is located close to a rock art site associated with the other entity.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0197f308190af7185fc9cc7a6e9 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.