Triple
T26487885
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Mary Rich |
E664872
|
entity |
| Predicate | nobleFamilyOfOrigin |
P143401
|
FINISHED |
| Object | Rich family, Earls of Warwick |
—
|
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: Rich family, Earls of Warwick | Statement: [Lady Mary Rich, nobleFamilyOfOrigin, Rich family, Earls of Warwick]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nobleFamilyOfOrigin Context triple: [Lady Mary Rich, nobleFamilyOfOrigin, Rich family, Earls of Warwick]
-
A.
fatherNobleFamily
Indicates that a person’s father belongs to, or is a member of, a specified noble family.
-
B.
associatedNobleFamily
Indicates a relationship where an entity is linked or connected to a particular noble family, typically by heritage, allegiance, or formal association.
-
C.
motherNobleFamily
Indicates that a person’s mother belongs to a specified noble family or house.
-
D.
hasNobleHouseOrigin
chosen
Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
-
E.
notableFamilyOrigin
Indicates that an entity is recognized for originating from, or being notably associated with, a particular family background or lineage.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612ffeb248190b8e7e6c773f0d951 |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:31 a.m.