Triple
T35127869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Horizon period of Andean chronology |
E1014357
|
entity |
| Predicate | timeInPrehistoryOf |
P113262
|
FINISHED |
| Object | Andean civilizations |
—
|
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: Andean civilizations | Statement: [Early Horizon period of Andean chronology, timeInPrehistoryOf, Andean civilizations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInPrehistoryOf Context triple: [Early Horizon period of Andean chronology, timeInPrehistoryOf, Andean civilizations]
-
A.
knownSincePrehistoricTimes
Indicates that the relationship or fact has been recognized or established by humans since prehistoric times, long before written history.
-
B.
chronologicalPeriodApprox
Indicates that one entity is associated with a time period that is approximately, but not exactly, the same as the time period of another entity.
-
C.
earliestKnownPeriod
chosen
Indicates the earliest historical or temporal period in which the subject is known or documented to have existed, occurred, or been relevant.
-
D.
historicPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
-
E.
eraChronology
Indicates the temporal ordering relationship that places an era within a specific position in a broader historical or chronological sequence.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:02 p.m.