Triple
T31475511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazca period |
E802980
|
entity |
| Predicate | hasRitualCenter |
P27744
|
FINISHED |
| Object | Cahuachi |
—
|
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: Cahuachi | Statement: [Nazca period, hasRitualCenter, Cahuachi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualCenter Context triple: [Nazca period, hasRitualCenter, Cahuachi]
-
A.
hasRitualSpace
chosen
Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
-
B.
hasCultPlaceType
Indicates that an entity is associated with a place used for cultic or religious activities of a specified type.
-
C.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
D.
hasMainAltarFor
Indicates that a specific altar serves as the primary or central altar designated for a particular entity, such as a church, chapel, or religious space.
-
E.
hasSacredPrecinct
Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 30, 2026, 9:28 p.m.