Triple
T19748791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marian Hour of Grace |
E474320
|
entity |
| Predicate | hasRecommendedTime |
P79788
|
FINISHED |
| Object | 12:00 noon to 1:00 p.m. |
—
|
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: 12:00 noon to 1:00 p.m. | Statement: [Marian Hour of Grace, hasRecommendedTime, 12:00 noon to 1:00 p.m.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecommendedTime Context triple: [Marian Hour of Grace, hasRecommendedTime, 12:00 noon to 1:00 p.m.]
-
A.
hasRecommendedActivity
Indicates that one entity suggests or endorses a particular activity for another entity to perform or engage in.
-
B.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
C.
hasTimeIndication
chosen
Indicates that something includes, specifies, or is associated with a particular time-related indication (such as a timestamp, time period, or temporal marker).
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
hasTimeOptions
Indicates that an entity is associated with one or more selectable time choices or configurations.
- 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_69d8e51940a0819087bd2996f98da668 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65296fa80819085aa4a18153531cf |
completed | April 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e5305016e08190b9561a96baecb0b8 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:47 p.m.