Triple
T34046535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polysomnography |
E873100
|
entity |
| Predicate | typicallyOccurs |
P171897
|
FINISHED |
| Object | overnight |
—
|
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: overnight | Statement: [Polysomnography, typicallyOccurs, overnight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyOccurs Context triple: [Polysomnography, typicallyOccurs, overnight]
-
A.
frequentOccasion
Indicates that a particular event, situation, or condition occurs repeatedly or commonly over time.
-
B.
typicallyObserves
Indicates that one entity, in the normal or usual course of events, observes, watches, or monitors another entity.
-
C.
usualFrequency
chosen
Indicates how often an action, event, or relationship typically occurs within a given time frame.
-
D.
phenomenonOccursDuring
Indicates that a phenomenon takes place within the temporal span or period defined by another event or condition.
-
E.
oftenSetIn
Indicates that something, such as a story or event, frequently takes place within a particular setting or context.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.