Triple
T8890744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Room |
E211653
|
entity |
| Predicate | handlesVisitType |
P5308
|
FINISHED |
| Object | Walk-in emergency visits |
—
|
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 emergency visits | Statement: [Emergency Room, handlesVisitType, Walk-in emergency visits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesVisitType Context triple: [Emergency Room, handlesVisitType, Walk-in emergency visits]
-
A.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
B.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
C.
typicalVisitorBehavior
Indicates the usual or characteristic way visitors act, respond, or interact in a given context or environment.
-
D.
canVisit
Indicates that one entity is permitted or able to go to or access another entity or location.
-
E.
hasTypeOfVisitorExperience
chosen
Indicates that an entity is associated with a particular category or kind of visitor experience it provides or involves.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc619188508190aacda410f0b4c98d |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:53 p.m.