Triple
T21489345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copa |
E530194
|
entity |
| Predicate | usedInStudiesOf |
P25490
|
FINISHED |
| Object | Recuay settlement patterns |
—
|
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: Recuay settlement patterns | Statement: [Copa, usedInStudiesOf, Recuay settlement patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInStudiesOf Context triple: [Copa, usedInStudiesOf, Recuay settlement patterns]
-
A.
hasResearchUse
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
B.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
C.
hasScientificStudy
Indicates that there exists a scientific study that investigates, analyzes, or provides evidence about the referenced entity or relationship.
-
D.
isStudiedUsing
Indicates that something serves as the method, tool, or approach by which something else is examined, analyzed, or researched.
-
E.
conditionStudied
Indicates that a particular condition (e.g., disease, state, or circumstance) is the focus of study or investigation in a given context.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea39e73081908e8d14118f9d1e03 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.