Triple
T29998000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Grey de Ruthyn |
E762082
|
entity |
| Predicate | titleHolderFromFamily |
P60633
|
FINISHED |
| Object | Grey family of Ruthin |
—
|
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: Grey family of Ruthin | Statement: [Baron Grey de Ruthyn, titleHolderFromFamily, Grey family of Ruthin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderFromFamily Context triple: [Baron Grey de Ruthyn, titleHolderFromFamily, Grey family of Ruthin]
-
A.
titleHeldByFamily
chosen
Indicates that a particular title, rank, or honor is held collectively or traditionally by a specific family or family line.
-
B.
titleHolderFrom
Indicates that an entity holds or has held a specific title or position starting from a given point in time.
-
C.
titleHolderName
Indicates the name of the person or entity that holds a particular title or position.
-
D.
titleHolderFullName
Indicates the full personal name of the entity that holds a particular title or position.
-
E.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: April 29, 2026, 6:40 p.m.