Triple
T11863075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presentation Sisters |
E282205
|
entity |
| Predicate | founderFeastDay |
P27473
|
FINISHED |
| Object | 26 April |
—
|
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: 26 April | Statement: [Presentation Sisters, founderFeastDay, 26 April]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: founderFeastDay Context triple: [Presentation Sisters, founderFeastDay, 26 April]
-
A.
feastDayObservedOn
chosen
Indicates that a particular feast day is celebrated or formally observed on a specified calendar date.
-
B.
foundingAround
Indicates that an entity was founded at approximately, but not exactly, the specified time or within a loosely defined surrounding period.
-
C.
foundingOf
Indicates the event or relationship in which an entity is established or created, typically linking the founder(s), the founded entity, and the time or context of its creation.
-
D.
celebratedDay
Indicates that a particular day is observed, honored, or festively recognized in association with an entity or event.
-
E.
foundedOnOccasionOf
Indicates that something was established or created specifically in response to, or to mark, a particular event or occasion.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a69b16bc8190999a0c1240f9ce6a |
completed | April 10, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69d8a2573dbc8190ab432e8e28fde6cc |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:43 p.m.