Triple
T27605561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Ingram |
E700169
|
entity |
| Predicate | hasFatherRoleIn |
P38221
|
FINISHED |
| Object | Ingram family case in Thurston County |
—
|
LITERAL FINISHED |
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: Ingram family case in Thurston County | Statement: [Paul Ingram, hasFatherRoleIn, Ingram family case in Thurston County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFatherRoleIn Context triple: [Paul Ingram, hasFatherRoleIn, Ingram family case in Thurston County]
-
A.
hasOwnerFatherOf
Indicates that the owner of an entity is the father of another specified entity.
-
B.
hasFatherFigure
Indicates that one entity serves as a paternal or father-like figure to another entity, regardless of biological relation.
-
C.
hasFamilyRole
chosen
Indicates that one entity holds a specific familial role or position in relation to another entity.
-
D.
hasMemberFather
Indicates that an entity is a member of a group or organization by virtue of their father’s membership or paternal relationship.
-
E.
hasReferentFather
Indicates that an entity’s referent is the father of 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_69ef6a4e2e208190b63b7268f405785c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 27, 2026, 2:09 p.m.