Triple
T20922626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExCeL London |
E515252
|
entity |
| Predicate | covid19Role |
P54174
|
FINISHED |
| Object | temporary critical care hospital site |
—
|
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: temporary critical care hospital site | Statement: [ExCeL London, covid19Role, temporary critical care hospital site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: covid19Role Context triple: [ExCeL London, covid19Role, temporary critical care hospital site]
-
A.
roleInRepertoire
Indicates that an entity serves a specific role or function within a larger repertoire, collection, or set of items.
-
B.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
C.
clinicalRole
chosen
Indicates the specific function, responsibility, or position an entity holds within a clinical or healthcare context.
-
D.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
E.
roleInDiseaseCycle
Indicates the specific function or contribution an entity has within the progression, transmission, or maintenance of a disease over time.
- 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f64f767481909deccd77b50bf4ae |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.