Triple
T13886126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitnem |
E333846
|
entity |
| Predicate | typicalTimeNight |
P26548
|
FINISHED |
| Object | before sleep for Kirtan Sohila |
—
|
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: before sleep for Kirtan Sohila | Statement: [Nitnem, typicalTimeNight, before sleep for Kirtan Sohila]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTimeNight Context triple: [Nitnem, typicalTimeNight, before sleep for Kirtan Sohila]
-
A.
associatedNightTiming
chosen
Indicates a relationship where an event, action, or condition is linked specifically to a time period occurring during the night.
-
B.
typicalEndHourLocal
Indicates the usual local-time clock hour at which an activity, event, or operation typically ends.
-
C.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
D.
nightService
Indicates that a service operates or is available during nighttime hours.
-
E.
typicalDSTChangeHour
Indicates the usual clock time at which a daylight saving time change (such as shifting clocks forward or backward) is applied.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a101488190bd790b28033d38b9 |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.