Triple
T26882280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marie of Blois |
E676937
|
entity |
| Predicate | partnerInDynasticAlliance |
P44810
|
FINISHED |
| Object | House of Anjou |
—
|
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: House of Anjou | Statement: [Marie of Blois, partnerInDynasticAlliance, House of Anjou]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInDynasticAlliance Context triple: [Marie of Blois, partnerInDynasticAlliance, House of Anjou]
-
A.
marriageAllianceWith
Indicates a formal marital union established between two parties to create or strengthen a political, social, or strategic alliance.
-
B.
rivalForMarriageOf
Indicates that one entity is a romantic competitor with another entity for the opportunity to marry a specific third entity.
-
C.
realmOfMarriageAlliance
Indicates a relationship where a marriage alliance is formed or exists within, or under the authority of, a particular realm or political domain.
-
D.
dynasticAlliance
chosen
Indicates a formal union or cooperative relationship established between ruling families or dynasties, typically through marriage or treaty, to secure mutual political or strategic advantage.
-
E.
marriageFormedBy
Indicates that a marriage relationship was created or brought into existence by a specific event, action, or process.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 5:40 a.m.