Triple
T2039291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogollon culture |
E44703
|
entity |
| Predicate | potteryDecoration |
P3351
|
FINISHED |
| Object | geometric designs |
—
|
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: geometric designs | Statement: [Mogollon culture, potteryDecoration, geometric designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: potteryDecoration Context triple: [Mogollon culture, potteryDecoration, geometric designs]
-
A.
decoration
chosen
Indicates that one entity serves as an ornament or embellishing element for another entity, enhancing its appearance or style.
-
B.
decorations
Indicates that one entity adds, provides, or serves as ornamental or decorative elements for another entity.
-
C.
traditionalCraft
Indicates that an entity is associated with or practices a craft or skill that is rooted in long-established, culturally transmitted traditions.
-
D.
throneDecoration
Indicates that one entity serves as a decorative element or ornamentation for a throne associated with another entity.
-
E.
traditionalArtForm
Indicates that something is an established artistic practice or style that has been handed down through cultural or historical tradition.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb951870481909dbdd8fc8b0c02fe |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.