Triple
T13671094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Childermas |
E327749
|
entity |
| Predicate | observedOnInTradition |
P111092
|
FINISHED |
| Object | 28 December in Western churches |
—
|
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: 28 December in Western churches | Statement: [Childermas, observedOnInTradition, 28 December in Western churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedOnInTradition Context triple: [Childermas, observedOnInTradition, 28 December in Western churches]
-
A.
viewOnTradition
Indicates an entity’s stance, perspective, or attitude toward a particular tradition or set of traditions.
-
B.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
C.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
D.
observedWhen
Indicates that one entity is observed or recorded at a specific time or under particular temporal conditions.
-
E.
traditionalLocationOfObservance
Indicates the place where an event, practice, or observance has been customarily or historically carried out.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc6599c248190b7f134b5b9947a23 |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.