Triple
T30664556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | statue of Ahuízotl |
E780623
|
entity |
| Predicate | subjectCulture |
P14191
|
FINISHED |
| Object | Mexica |
—
|
NE NERFINISHED |
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: Mexica | Statement: [statue of Ahuízotl, subjectCulture, Mexica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectCulture Context triple: [statue of Ahuízotl, subjectCulture, Mexica]
-
A.
culturalCategory
Indicates that one entity classifies or groups another entity according to a particular culture, tradition, or culturally defined type.
-
B.
usesCulture
Indicates that one entity employs, incorporates, or relies on the cultural practices, norms, or artifacts associated with another entity in its actions or functioning.
-
C.
aboutCulture
Indicates that something concerns, references, or is related to a particular culture, its practices, values, or expressions.
-
D.
culturalType
Indicates the classification of something according to its cultural category, style, or tradition.
-
E.
culturalSphere
chosen
Indicates that one entity belongs to, is influenced by, or participates in the cultural domain, tradition, or milieu defined by another entity.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 29, 2026, 8:31 p.m.