Triple
T25500421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andean archaeology |
E639095
|
entity |
| Predicate | studiesCulture |
P149875
|
FINISHED |
| Object | Moche |
—
|
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: Moche | Statement: [Andean archaeology, studiesCulture, Moche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studiesCulture Context triple: [Andean archaeology, studiesCulture, Moche]
-
A.
cultureStudied
chosen
Indicates that an entity has examined, researched, or analyzed a particular culture as the object of study.
-
B.
culturalSphere
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
-
C.
ethnicCultureDocumented
Indicates that information about an ethnic culture has been recorded, described, or otherwise documented.
-
D.
culturalInterest
Indicates a relationship where one entity has an interest in, appreciation for, or engagement with the culture, traditions, or cultural expressions associated with another entity.
-
E.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 2:42 p.m.