Triple
T34046536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polysomnography |
E873100
|
entity |
| Predicate | typicallyPerformedIn |
P75511
|
FINISHED |
| Object | sleep laboratory |
—
|
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: sleep laboratory | Statement: [Polysomnography, typicallyPerformedIn, sleep laboratory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyPerformedIn Context triple: [Polysomnography, typicallyPerformedIn, sleep laboratory]
-
A.
commonlyPerformedIn
chosen
Indicates that an action or activity is typically or frequently carried out within a particular context, location, or setting.
-
B.
frequentlyPerformedAt
Indicates that an action or event occurs regularly or with high frequency at a particular location or context.
-
C.
sometimesPracticedAt
Indicates that an activity or practice occurs at a particular place or time on some occasions, but not regularly or consistently.
-
D.
commonlyPerformedAs
Indicates that an action, behavior, or role is typically or frequently carried out in a particular manner, form, or context.
-
E.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
- 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.