Triple
T21490226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galton family |
E530216
|
entity |
| Predicate | laterReligiousStatus |
P114481
|
FINISHED |
| Object | largely non-Quaker |
—
|
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: largely non-Quaker | Statement: [Galton family, laterReligiousStatus, largely non-Quaker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterReligiousStatus Context triple: [Galton family, laterReligiousStatus, largely non-Quaker]
-
A.
religiousStatus
Indicates the religious affiliation, role, or standing that an entity holds within a religious context.
-
B.
religiousAffiliationLater
chosen
Indicates that an entity’s religious affiliation at a later time is the specified religion or organization.
-
C.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
D.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
E.
roleInStateReligion
Indicates that an entity holds a specific function, position, or involvement within the officially recognized religion of a state.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea3aee648190ba845f0c7d8110dd |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.