Triple
T14892952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Vigils |
E359796
|
entity |
| Predicate | isAssociatedWithTimeOfDay |
P6019
|
FINISHED |
| Object | night |
—
|
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: night | Statement: [Office of Vigils, isAssociatedWithTimeOfDay, night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAssociatedWithTimeOfDay Context triple: [Office of Vigils, isAssociatedWithTimeOfDay, night]
-
A.
hasTimeOfDay
chosen
Indicates that a situation, event, or state occurs during, or is associated with, a specific part of the day (e.g., morning, afternoon, evening, night).
-
B.
associatedWithTime
Indicates a relationship where something is linked or connected to a specific point or period in time.
-
C.
operatesAtTime
Indicates that an action, process, or system is functioning or active during a specified time or time interval.
-
D.
timeOfDayCoverage
Indicates the specific portion or range of the day during which an activity, service, or condition is in effect or applicable.
-
E.
observesSameTimeAs
Indicates that two observation events occur simultaneously or during the same time interval.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f9d10c819091732d7a5a42a682 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:10 a.m.