Triple
T37124156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingapirca archaeological complex |
E919343
|
entity |
| Predicate | earlierCulture |
P192185
|
FINISHED |
| Object | Cañari people |
—
|
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: Cañari people | Statement: [Ingapirca archaeological complex, earlierCulture, Cañari people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierCulture Context triple: [Ingapirca archaeological complex, earlierCulture, Cañari people]
-
A.
earlierCulturalSphere
Indicates that one cultural sphere existed or was influential before another in time.
-
B.
earlierFortificationCulture
Indicates that one culture’s fortification activity or tradition chronologically precedes that of another culture.
-
C.
earliestArchaeologicalCulture
Indicates that one archaeological culture is the earliest known or first in time within a specified sequence, region, or context.
-
D.
earlierCultOnSite
Indicates that a religious cult or worship practice existed at a location prior to the one currently under consideration.
-
E.
culturalPeriod
Indicates the historical or cultural era with which an entity is associated or during which it was created, used, or significant.
- F. None of above. chosen
Provenance (4 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_69f76e9d13e48190a108f7fbf80ff375 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
| PDg | Predicate description generation | batch_69fcf82405c88190a19cecf8e9cc272d |
completed | May 7, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:15 p.m.