Triple
T30251184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryder Trauma Center |
E769203
|
entity |
| Predicate | traumaServices |
P169025
|
FINISHED |
| Object | Adult trauma care |
—
|
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: Adult trauma care | Statement: [Ryder Trauma Center, traumaServices, Adult trauma care]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traumaServices Context triple: [Ryder Trauma Center, traumaServices, Adult trauma care]
-
A.
hasTraumaCenter
Indicates that an entity (such as a hospital or facility) includes or is equipped with a designated trauma center capable of providing specialized emergency care for severe injuries.
-
B.
trauma
Indicates that an entity has experienced a deeply distressing or harmful event or series of events that cause lasting psychological or emotional impact.
-
C.
traumaSource
Indicates that one entity is the origin or cause of another entity’s trauma.
-
D.
traumaLevel
Indicates the degree or severity of trauma experienced or present in relation to an entity or event.
-
E.
traumaTheme
Indicates that the relationship or context involves themes of trauma, such as psychological injury, distressing experiences, or their emotional and narrative impact.
- 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_69f224831dc08190b2e569b987264057 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6807ab42c819098d70c25bfc42ffd |
completed | May 2, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:40 p.m.