Triple
T35127875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Horizon period of Andean chronology |
E1014357
|
entity |
| Predicate | hasKeyArtStyle |
P1609
|
FINISHED |
| Object | Chavín art style |
—
|
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: Chavín art style | Statement: [Early Horizon period of Andean chronology, hasKeyArtStyle, Chavín art style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyArtStyle Context triple: [Early Horizon period of Andean chronology, hasKeyArtStyle, Chavín art style]
-
A.
hasKeyArtifact
Indicates that an entity possesses or is associated with a crucial or central artifact relevant to a particular context or process.
-
B.
hasArtFeature
Indicates that an entity possesses or is characterized by a particular artistic attribute, element, or stylistic feature.
-
C.
hasAlbumStyle
Indicates that an album is associated with a particular artistic, musical, or design style.
-
D.
hasStyle
chosen
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
E.
hasSignatureVisualStyle
Indicates that an entity is characterized by a distinctive and recognizable visual style that sets it apart from others.
- 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_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:02 p.m.