Triple
T35127872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Horizon period of Andean chronology |
E1014357
|
entity |
| Predicate | usedInChronologicalSystemBy |
P104021
|
FINISHED |
| Object | Andean archaeologists |
—
|
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: Andean archaeologists | Statement: [Early Horizon period of Andean chronology, usedInChronologicalSystemBy, Andean archaeologists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInChronologicalSystemBy Context triple: [Early Horizon period of Andean chronology, usedInChronologicalSystemBy, Andean archaeologists]
-
A.
usedInCalendarSystem
Indicates that something (such as a time unit, era, or convention) is employed as part of a particular calendar system.
-
B.
chronologyUsedBy
chosen
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
C.
usedForChronology
Indicates that something is employed to establish, organize, or reference the order and timing of events.
-
D.
chronologyType
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
E.
usesJulianCalendar
Indicates that the subject follows or is based on the Julian calendar system for dating events or timekeeping.
- 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_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
Created at: May 3, 2026, 4:02 p.m.