Triple
T9961233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Triqui people |
E195573
|
entity |
| Predicate | textileCharacteristic |
P64189
|
FINISHED |
| Object | red background |
—
|
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: red background | Statement: [Triqui people, textileCharacteristic, red background]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textileCharacteristic Context triple: [Triqui people, textileCharacteristic, red background]
-
A.
textileFeature
chosen
Indicates a characteristic, property, or notable aspect associated with a textile or fabric.
-
B.
textileType
Indicates the specific kind or category of textile material associated with an entity.
-
C.
fiberCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a fiber or fibrous material.
-
D.
fashionCharacteristic
Indicates a relationship where one entity possesses or exhibits a particular style, trend, or fashion-related attribute in relation to another.
-
E.
typicalFabric
Indicates that something is made from or associated with a fabric material that is standard or characteristic for its 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6d219c48190b2084b0eb07ae125 |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.