Triple
T26527752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Devon (English Courtenay branch) |
E670737
|
entity |
| Predicate | hasNobleFamilyReligion |
P27867
|
FINISHED |
| Object | Christianity |
—
|
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: Christianity | Statement: [Earl of Devon (English Courtenay branch), hasNobleFamilyReligion, Christianity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobleFamilyReligion Context triple: [Earl of Devon (English Courtenay branch), hasNobleFamilyReligion, Christianity]
-
A.
hasNobleHouseOrigin
Indicates that an entity originates from, or is ancestrally associated with, a particular noble house.
-
B.
hasLiturgicalFamily
Indicates that one religious rite, tradition, or practice belongs to, or is classified under, a broader liturgical family or lineage.
-
C.
hasPriestlyLineage
Indicates that an entity descends from, or belongs to, a recognized priestly family or hereditary priestly line.
-
D.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
-
E.
associatedReligiousFamily
Indicates a relationship where an entity is linked or connected to a particular religious family or tradition.
- 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_69eeb31ea1e08190b9ff43cf9bc25bf8 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: April 27, 2026, 1:33 a.m.