Triple
T1087105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Entrance |
E24076
|
entity |
| Predicate | timeWithinService |
P6261
|
FINISHED |
| Object | after the Liturgy of the Word |
—
|
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: after the Liturgy of the Word | Statement: [Great Entrance, timeWithinService, after the Liturgy of the Word]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeWithinService Context triple: [Great Entrance, timeWithinService, after the Liturgy of the Word]
-
A.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
timePeriodWithin
chosen
Indicates that one time period is entirely contained within the bounds of another time period.
-
C.
timeToComplete
Indicates the duration required for an entity or process to be fully completed.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
timingMethod
Indicates the method or technique used to measure or record the timing of an event or process.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.