Triple
T11274157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mother most amiable |
E266887
|
entity |
| Predicate | positionInLitany |
P98875
|
FINISHED |
| Object | one of the maternal titles of Mary |
—
|
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: one of the maternal titles of Mary | Statement: [Mother most amiable, positionInLitany, one of the maternal titles of Mary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInLitany Context triple: [Mother most amiable, positionInLitany, one of the maternal titles of Mary]
-
A.
positionInLent
Indicates the specific point or stage an event, day, or period occupies within the overall timeline of Lent.
-
B.
positionOnLiturgy
Indicates the stance or viewpoint an entity holds regarding liturgical practices, forms, or regulations.
-
C.
positionNumber
Indicates the specific ordinal or identifying number assigned to a position within an ordered set or organizational structure.
-
D.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
E.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
- F. None of above. chosen
Provenance (4 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_69d6aac8c2f48190ad0596f1f89f0470 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e965c9048190804ebb48f0a4817b |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a240588190aa097298f951c915 |
completed | April 9, 2026, 11:04 a.m. |
| PDg | Predicate description generation | batch_69d796cf74308190a5b29d0dd82954a2 |
completed | April 9, 2026, 12:08 p.m. |
Created at: April 8, 2026, 9:31 p.m.