Triple
T38653972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Bedford |
E939837
|
entity |
| Predicate | holderFamilyInfluenceArea |
P114304
|
FINISHED |
| Object | Bedfordshire |
—
|
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: Bedfordshire | Statement: [Earl of Bedford, holderFamilyInfluenceArea, Bedfordshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderFamilyInfluenceArea Context triple: [Earl of Bedford, holderFamilyInfluenceArea, Bedfordshire]
-
A.
familyInfluenceArea
chosen
Indicates the domain or scope within which a family exerts influence, impact, or control over something or someone.
-
B.
parentInfluence
Indicates that one entity has a formative or guiding effect on another entity in the role of a parent.
-
C.
impactOnFamily
Indicates the effect or influence that something has on a family’s situation, dynamics, or well-being.
-
D.
familyInvolvement
Indicates that there is participation, engagement, or influence of family members in the context of a particular activity, decision, or situation.
-
E.
familyAffectedBy
Indicates that one or more members of a person’s family experience or are impacted by a specified condition, event, or circumstance.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:33 p.m.