Triple
T37001194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlton Campus emergency department |
E915353
|
entity |
| Predicate | emergencyAccess |
P186894
|
FINISHED |
| Object | walk-in |
—
|
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: walk-in | Statement: [Charlton Campus emergency department, emergencyAccess, walk-in]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emergencyAccess Context triple: [Charlton Campus emergency department, emergencyAccess, walk-in]
-
A.
emergencyUse
Indicates that something is being used in response to an urgent or critical situation, typically as a temporary or exceptional measure.
-
B.
emergencyService
Indicates that one entity provides or is associated with urgent, time-critical assistance or response to another entity in emergency situations.
-
C.
emergencyOffice
Indicates that an office or location serves as an emergency contact point or coordination center for urgent or crisis situations.
-
D.
emergencyProvision
Indicates a temporary measure or resource activated specifically to address urgent or crisis situations.
-
E.
emergencyRole
Indicates that an entity holds a specific function, responsibility, or authority in emergency or crisis situations.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.