Triple
T25928690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xochipilli |
E653374
|
entity |
| Predicate | possibleConsort |
P115401
|
FINISHED |
| Object | Mayahuel |
—
|
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: Mayahuel | Statement: [Xochipilli, possibleConsort, Mayahuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleConsort Context triple: [Xochipilli, possibleConsort, Mayahuel]
-
A.
possibleConsortOf
chosen
Indicates that one entity is a potential or likely romantic or marital partner of another, without asserting that the relationship is confirmed.
-
B.
notableConsort
Indicates that one entity is a spouse or consort of another who is notable or significant in some recognized context.
-
C.
producedConsortOf
Indicates a relationship where one entity created, authored, or otherwise brought into existence another entity that serves as a consort (spouse or partner) to a third entity.
-
D.
motherIsConsortOf
Indicates that the subject’s mother is the consort (spouse or official partner) of the specified person.
-
E.
hasConsortCrowned
Indicates that an individual has a spouse or consort who has been formally crowned, typically in a royal or ceremonial context.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 22, 2026, 8:36 a.m.