Triple
T28279619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huasteca culture |
E713103
|
entity |
| Predicate | hadDeitiesInCommonWith |
P32474
|
FINISHED |
| Object | other Mesoamerican cultures |
—
|
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: other Mesoamerican cultures | Statement: [Huasteca culture, hadDeitiesInCommonWith, other Mesoamerican cultures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadDeitiesInCommonWith Context triple: [Huasteca culture, hadDeitiesInCommonWith, other Mesoamerican cultures]
-
A.
sharesDeitiesWith
chosen
Indicates that two entities have one or more deities in common within their respective religious or mythological systems.
-
B.
comparableDeity
Indicates that one deity is considered comparable to another in terms of role, attributes, status, or function.
-
C.
worshippedAlongside
Indicates that two deities or sacred figures were venerated together within the same religious context, ritual, or cult practice.
-
D.
hasNumberOfDeities
Indicates the specific count of deities associated with an entity, such as a religion, mythology, or belief system.
-
E.
hasSiblingDeity
Indicates that one deity is a sibling (sharing at least one parent) of another deity.
- 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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6444ef12481909d3c98e5d5660117 |
completed | May 2, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:21 p.m.