Triple
T17284338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casma |
E419611
|
entity |
| Predicate | hasNearbyHeritage |
P14422
|
FINISHED |
| Object | pre-Columbian sites |
—
|
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: pre-Columbian sites | Statement: [Casma, hasNearbyHeritage, pre-Columbian sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHeritage Context triple: [Casma, hasNearbyHeritage, pre-Columbian sites]
-
A.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
B.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
C.
hasNearbyArchaeologicalSite
chosen
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
D.
hasNearbyCulturalDistrict
Indicates that an entity is located close to a designated cultural district or area with concentrated cultural activities.
-
E.
hasAdjacentHistoricSite
Indicates that one place is directly next to or very near another place that is recognized as a historic 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e4332bd324819080795152293d6d43 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:40 a.m.