Triple
T30170302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Coruña |
E766900
|
entity |
| Predicate | isTiedToFamily |
P7844
|
FINISHED |
| Object | House of Mendoza |
—
|
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 Mendoza | Statement: [Count of Coruña, isTiedToFamily, House of Mendoza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTiedToFamily Context triple: [Count of Coruña, isTiedToFamily, House of Mendoza]
-
A.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
B.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
C.
treatsAsFamily
Indicates that one entity regards and behaves toward another with the closeness, care, and obligations typically reserved for family members.
-
D.
hasFamilyRole
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
E.
identifiedAsFamilyIn
Indicates that one entity is recognized or designated as a family member within the context of a specified group, record, or setting.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f0b25908190baf7f9dfef6ec6ce |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:24 p.m.