Triple
T10969172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Sunday of Quadragesima |
E259185
|
entity |
| Predicate | hasPositionInSeason |
P51004
|
FINISHED |
| Object | second Sunday of Lent |
—
|
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: second Sunday of Lent | Statement: [Second Sunday of Quadragesima, hasPositionInSeason, second Sunday of Lent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionInSeason Context triple: [Second Sunday of Quadragesima, hasPositionInSeason, second Sunday of Lent]
-
A.
positionInSeason
chosen
Indicates the specific ordinal placement or ranking of something within the sequence of items in a season.
-
B.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
C.
hostedInSeason
Indicates that an event, show, or activity took place or was held during a specific season.
-
D.
playsInPosition
Indicates that an entity (typically a player) performs or operates in a specific role or position within a game, sport, or activity.
-
E.
hasSeason
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77198e5408190904b2bb603d1bc16 |
completed | April 9, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.