Triple
T25511030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sister Luke |
E639378
|
entity |
| Predicate | takesReligiousName |
P146129
|
FINISHED |
| Object | Sister Luke |
—
|
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: Sister Luke | Statement: [Sister Luke, takesReligiousName, Sister Luke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesReligiousName Context triple: [Sister Luke, takesReligiousName, Sister Luke]
-
A.
hasReligiousName
chosen
Indicates that an entity possesses a name specifically associated with a religious context, role, or tradition.
-
B.
religiousNamesake
Indicates that one entity serves as the religiously significant figure, concept, or object after which the other entity is named.
-
C.
hasReligiousAffiliationInName
Indicates that an entity’s name explicitly includes or reflects a religious affiliation or association.
-
D.
religiousName
Indicates that an entity has or is known by a name specifically associated with a religious role, identity, or context.
-
E.
hasNameDayOrReligiousUsage
Indicates that an entity has an associated name day celebration or is used in a religious or liturgical context.
- 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80b05ac8190a4a0cd75e8717917 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:49 p.m.