Triple
T36667112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of the Meeting of Our Lord |
E905295
|
entity |
| Predicate | concludingPeriod |
P186146
|
FINISHED |
| Object | afterfeast |
—
|
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: afterfeast | Statement: [Feast of the Meeting of Our Lord, concludingPeriod, afterfeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concludingPeriod Context triple: [Feast of the Meeting of Our Lord, concludingPeriod, afterfeast]
-
A.
finalPeriodAssociatedWith
Indicates that something is linked to or occurs during the last relevant time period in a sequence or lifecycle.
-
B.
concludedDuring
Indicates that an event, process, or state ended within the temporal bounds of another specified time period or event.
-
C.
concludesIn
Indicates that an event, process, or action ends or reaches its final state within a specified time, place, or context.
-
D.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
-
E.
focusPeriodEnd
Indicates the point in time at which a specified focus period or interval concludes.
- 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_69f76e6f10008190aea41746aa1b186e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.