Triple
T6113575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tepanec |
E136303
|
entity |
| Predicate | pantheonSharedWith |
P32062
|
FINISHED |
| Object | other Nahua peoples |
—
|
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 Nahua peoples | Statement: [Tepanec, pantheonSharedWith, other Nahua peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pantheonSharedWith Context triple: [Tepanec, pantheonSharedWith, other Nahua peoples]
-
A.
sharesMembersWith
Indicates that two groups or collections have one or more members in common.
-
B.
sharedPantheonWith
chosen
Indicates that two deities or mythological figures belong to or are worshiped within the same religious pantheon or mythological tradition.
-
C.
homeGroundSharedWith
Indicates that two teams or organizations use the same venue or location as their home ground.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesAdministrationWith
Indicates that two entities are jointly managed, governed, or overseen by the same administrative body or authority.
- 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bbf2ee4819097af2cce9248bf4e |
completed | March 22, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.