Triple
T23881773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lygon family |
E600221
|
entity |
| Predicate | notableTitleAssociation |
P154324
|
FINISHED |
| Object | Earl Beauchamp |
—
|
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: Earl Beauchamp | Statement: [Lygon family, notableTitleAssociation, Earl Beauchamp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTitleAssociation Context triple: [Lygon family, notableTitleAssociation, Earl Beauchamp]
-
A.
notableTitleType
Indicates that a title associated with an entity is of a type considered notable or especially significant.
-
B.
notableTitleOnTheLine
Indicates that a significant or prestigious title is at stake or being contested in the associated event or context.
-
C.
notableRelatedList
Indicates that there exists a curated or recognized list that is notably related to the subject, typically grouping it with similar or thematically connected entities.
-
D.
notableDisplay
Indicates that something is prominently or distinctively presented in a way that draws special attention or recognition.
-
E.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc05e4d48190864fc47bdffa4ca9 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:24 p.m.