Triple
T12147174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zona Arqueológica de Cuicuilco |
E289354
|
entity |
| Predicate | partiallyCoveredBy |
P16474
|
FINISHED |
| Object | lava from Xitle volcano |
—
|
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: lava from Xitle volcano | Statement: [Zona Arqueológica de Cuicuilco, partiallyCoveredBy, lava from Xitle volcano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyCoveredBy Context triple: [Zona Arqueológica de Cuicuilco, partiallyCoveredBy, lava from Xitle volcano]
-
A.
partlyCoveredBy
chosen
Indicates that one entity is covered or overlapped by another entity, but only to a partial extent rather than completely.
-
B.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
-
C.
partlyProtectedBy
Indicates that an entity is only partially safeguarded or covered by a specified protective measure, not fully protected.
-
D.
isCoveredBy
Indicates that one entity is physically or conceptually overlaid, protected, or enclosed by another entity.
-
E.
isPartially
Indicates that one entity is included within another to some extent, but not completely or fully.
- 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_69d6ab4c6710819097a9d228382dde43 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d915d7109481908bf5fe512bba3c89 |
completed | April 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69d9150c18148190bf8152189c0e5fca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.