Triple
T37497974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvira Menéndez |
E931880
|
entity |
| Predicate | monarchConsortDuringReignOf |
P9813
|
FINISHED |
| Object | Ordoño II of León |
—
|
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: Ordoño II of León | Statement: [Elvira Menéndez, monarchConsortDuringReignOf, Ordoño II of León]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchConsortDuringReignOf Context triple: [Elvira Menéndez, monarchConsortDuringReignOf, Ordoño II of León]
-
A.
monarchConsortInDynasty
Indicates that a person served as the consort (spouse) of a reigning monarch within a specified dynasty.
-
B.
monarchConsortOf
chosen
Indicates that one person is the spouse of a reigning monarch, holding the role of consort to that monarch.
-
C.
monarchOfWhomConsort
Indicates that a person is the monarch (king/queen/ruler) of another person who is their consort (spouse).
-
D.
monarchDuringTerm
Indicates that a specified monarch was the reigning sovereign during the time span of a given officeholder’s term.
-
E.
monarchOfConsort
Indicates that one entity is the consort (spouse) of the reigning monarch of another entity (typically a state or territory).
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.