Triple
T34765384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleanor of Portugal |
E1002196
|
entity |
| Predicate | maritalStatusWithPeterIV |
P181821
|
FINISHED |
| Object | brief marriage |
—
|
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: brief marriage | Statement: [Eleanor of Portugal, maritalStatusWithPeterIV, brief marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maritalStatusWithPeterIV Context triple: [Eleanor of Portugal, maritalStatusWithPeterIV, brief marriage]
-
A.
maritalStatusWithFerdinandI
Indicates that an entity has a specific marital relationship or status in relation to Ferdinand I.
-
B.
maritalStatusAfterIvanIV
Indicates the marital status a person has following the reign or lifetime of Ivan IV.
-
C.
followedByInPhilipIIMarriages
Indicates that one marriage chronologically succeeds another within the sequence of marriages of Philip II.
-
D.
endTimeOfMarriageWithPeterIII
Indicates the date and time when a marriage involving Peter III officially ended.
-
E.
marriageToHenryVIIIStatus
Indicates the status or condition of an entity’s marriage relationship to Henry VIII (e.g., current, former, annulled, pending, etc.).
- F. None of above. chosen
Provenance (4 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: May 3, 2026, 3:59 p.m.