Triple
T27240800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Ormond |
E687202
|
entity |
| Predicate | principalFamily |
P102867
|
FINISHED |
| Object | Butler family |
—
|
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: Butler family | Statement: [House of Ormond, principalFamily, Butler family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: principalFamily Context triple: [House of Ormond, principalFamily, Butler family]
-
A.
primaryFamily
chosen
Indicates that one entity is the main or principal family unit to which another entity is most closely or formally associated.
-
B.
ownerFamily
Indicates that a family has ownership or proprietary rights over a particular entity or resource.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
topFamily
Indicates that the subject entity belongs to the highest-ranking or primary family group within a given hierarchy or classification.
-
E.
mainPartyFamily
Indicates that one entity is a primary party in a relationship or event and the other entity is a family member associated with that main party.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 27, 2026, 10:37 a.m.