Triple
T29955037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arms of Grey of Ruthyn |
E760874
|
entity |
| Predicate | armigeralFamily |
P168295
|
FINISHED |
| Object | House of Grey |
—
|
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 Grey | Statement: [Arms of Grey of Ruthyn, armigeralFamily, House of Grey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armigeralFamily Context triple: [Arms of Grey of Ruthyn, armigeralFamily, House of Grey]
-
A.
isaFamily
Indicates that one entity is a family member or belongs to the same family group as another entity.
-
B.
designFamily
Indicates a relationship where one entity belongs to, or is categorized within, a particular design family or style group defined by another entity.
-
C.
familyOf
Indicates a familial relationship exists between the entities, such as by blood, marriage, or adoption.
-
D.
primeMoverFamily
Indicates that one entity is the primary driving or originating force behind another within a familial or foundational relationship.
-
E.
designedByFamilyOf
Indicates that something was created, planned, or conceived by one or more members of a particular family or familial group.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f678397b6c8190938dd43f8f30f229 |
completed | May 2, 2026, 10:18 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:27 p.m.