Triple
T31475521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazca period |
E802980
|
entity |
| Predicate | timeInAndeanSequence |
P138941
|
FINISHED |
| Object | Early Intermediate Period |
—
|
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: Early Intermediate Period | Statement: [Nazca period, timeInAndeanSequence, Early Intermediate Period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInAndeanSequence Context triple: [Nazca period, timeInAndeanSequence, Early Intermediate Period]
-
A.
timeInAztecYear
Indicates that a specific time or date occurs within a particular year as defined by the Aztec calendar system.
-
B.
timeInSeries
Indicates that one temporal value occurs within the duration or sequence span defined by another in a series.
-
C.
timePeriodInSeries
chosen
Indicates the specific time span or interval during which an installment, episode, or part occurs within a larger series or sequence.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
timeIndexed
Indicates that the relationship or property it connects is associated with, or valid during, a specific time or time interval.
- 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_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 9:28 p.m.