Triple
T32249559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Centre for Infectious Diseases |
E823844
|
entity |
| Predicate | hasIsolationRooms |
P176054
|
FINISHED |
| Object | negative-pressure rooms |
—
|
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: negative-pressure rooms | Statement: [National Centre for Infectious Diseases, hasIsolationRooms, negative-pressure rooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIsolationRooms Context triple: [National Centre for Infectious Diseases, hasIsolationRooms, negative-pressure rooms]
-
A.
hasIsolation
Indicates that an entity is separated or kept apart from others, typically to prevent interaction, influence, or contamination.
-
B.
hasSingleRooms
Indicates that an entity offers or includes individual rooms intended for single occupancy.
-
C.
hasInpatientBeds
Indicates that an entity provides or is equipped with beds designated for admitting and treating inpatients.
-
D.
hasStateRooms
Indicates that an entity (such as a ship, building, or facility) contains or is equipped with state rooms.
-
E.
hasPeriodRooms
Indicates that an entity contains rooms that are decorated or preserved to reflect specific historical periods.
- 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_69f3490cdda88190a9d61e11252a771f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 12:40 a.m.