Triple
T20439100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamegroute |
E501334
|
entity |
| Predicate | traditionalPotteryColor |
P127985
|
FINISHED |
| Object | green |
—
|
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: green | Statement: [Tamegroute, traditionalPotteryColor, green]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalPotteryColor Context triple: [Tamegroute, traditionalPotteryColor, green]
-
A.
potteryColor
chosen
Indicates the color attribute associated with a piece of pottery.
-
B.
hasPotteryType
Indicates that an entity is associated with or characterized by a specific type or category of pottery.
-
C.
traditionalHomeColor
Indicates the customary or historically typical color associated with a home in a given cultural or regional tradition.
-
D.
traditionalKitColor
Indicates the customary or historically established color scheme used for an entity’s standard or primary kit or uniform.
-
E.
eraOfPorcelain
Indicates the historical period or era during which a particular style or type of porcelain was produced or prominent.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f112e48190a3af818c0f6ee839 |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.