Triple
T36667114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feast of the Meeting of Our Lord |
E905295
|
entity |
| Predicate | afterfeastLength |
P186528
|
FINISHED |
| Object | 7 days (in Byzantine usage) |
—
|
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: 7 days (in Byzantine usage) | Statement: [Feast of the Meeting of Our Lord, afterfeastLength, 7 days (in Byzantine usage)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterfeastLength Context triple: [Feast of the Meeting of Our Lord, afterfeastLength, 7 days (in Byzantine usage)]
-
A.
forefeastLength
Indicates the duration or number of days that a forefeast (the preparatory period before a main feast) lasts.
-
B.
hasAfterfeast
Indicates that one event, celebration, or feast occurs as a follow-up or continuation after another feast.
-
C.
feastEndsOn
Indicates that a feast or celebratory event concludes on a specific date or time.
-
D.
extendedFeast
Indicates a situation where a feast or celebratory meal continues for an unusually long or prolonged period of time.
-
E.
feastRetainedIn
Indicates that a particular feast or celebration is preserved, maintained, or kept within a specific context, location, or system.
- 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_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:12 p.m.