Triple
T37934095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Orléans e Bragança |
E946297
|
entity |
| Predicate | originFromMaternalLine |
P50958
|
FINISHED |
| Object | House of Braganza |
E109851
|
NE 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: House of Braganza | Statement: [de Orléans e Bragança, originFromMaternalLine, House of Braganza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originFromMaternalLine Context triple: [de Orléans e Bragança, originFromMaternalLine, House of Braganza]
-
A.
maternalAncestorOf
Indicates that one entity is an ancestor of another specifically through a chain of maternal (mother-to-child) relationships.
-
B.
originCountryOfPaternalLine
Indicates the country from which a person’s paternal family line (through the father’s side) originates.
-
C.
hasPatrilinealOrigin
Indicates that something originates from or is derived through the male (father’s) ancestral line.
-
D.
hasMotherOrigin
chosen
Indicates that an entity’s origin, source, or lineage is derived from or attributed to a mother entity.
-
E.
sourceOfLineageFor
Indicates that one entity serves as the origin or ancestral source from which another entity’s lineage is derived.
- F. None of above.
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_69f76ef3b7248190892fb9706423be7c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d1e75a881909d0706a77854f10a |
completed | June 28, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.