Triple
T34111790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nitnem |
E874856
|
entity |
| Predicate | prescribedTime |
P178242
|
FINISHED |
| Object | morning |
—
|
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: morning | Statement: [Nitnem, prescribedTime, morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prescribedTime Context triple: [Nitnem, prescribedTime, morning]
-
A.
timeToAdminister
Indicates the scheduled or required amount of time needed to administer a treatment, procedure, or action to a subject.
-
B.
prescribedIn
Indicates that something (typically a medication, treatment, or procedure) has been formally ordered or recommended within a specific context, such as a prescription, order, or medical record.
-
C.
administeredBefore
Indicates that one treatment, medication, or intervention was given to a subject at an earlier time than another specified treatment, medication, or intervention.
-
D.
operatesAtTime
Indicates that an action, process, or system is functioning or active during a specified time or time interval.
-
E.
presentedAtTime
Indicates that an event, action, or item was presented or occurred at a specific point in time.
- F. None of above. chosen
Provenance (4 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_69f349a80d4481908527317d43f5c579 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70cb544848190aaeb8f766a95aaff |
completed | May 3, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:53 a.m.