Triple
T12460000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inca people |
E297761
|
entity |
| Predicate | textileProduction |
P64189
|
FINISHED |
| Object | high-quality textiles |
—
|
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: high-quality textiles | Statement: [Inca people, textileProduction, high-quality textiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textileProduction Context triple: [Inca people, textileProduction, high-quality textiles]
-
A.
textileType
Indicates the specific kind or category of textile material associated with an entity.
-
B.
textileFeature
chosen
Indicates a characteristic, property, or notable aspect associated with a textile or fabric.
-
C.
typicalFabric
Indicates that something is made from or associated with a fabric material that is standard or characteristic for its type.
-
D.
weavingCenter
Indicates that an entity serves as a central place or hub where weaving activities are carried out or coordinated.
-
E.
fiberwiseDescription
Indicates a description or characterization that is given separately for each fiber in a fibered or parameterized structure, specifying how the relationship or action behaves over individual fibers.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95151e7348190a1d4953a8b416a13 |
completed | April 10, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69d94d3c27a08190a0237200203e476d |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.