Triple
T31826406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Communications Division (Orange County Sheriff’s Office) |
E812406
|
entity |
| Predicate | typeOfCall |
P4224
|
FINISHED |
| Object | 911 emergency calls |
—
|
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: 911 emergency calls | Statement: [Communications Division (Orange County Sheriff’s Office), typeOfCall, 911 emergency calls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCall Context triple: [Communications Division (Orange County Sheriff’s Office), typeOfCall, 911 emergency calls]
-
A.
callType
Indicates the category or nature of a call (such as its purpose, direction, or handling), distinguishing one kind of call from another.
-
B.
typeOf
chosen
Indicates that one entity is a specific kind, class, or category instance of another more general entity.
-
C.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
D.
typeOfCallCenter
Indicates the specific category or kind of call center associated with or operated by an entity.
-
E.
callsTo
Indicates that one entity initiates a call or communication action directed toward another entity.
- 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_69f348e97fa48190aa06286962af6dee |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a0017dd31d08190aa5e9f72df83733a |
completed | May 10, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_6a0015a1deb88190b9cdaa60455b0a33 |
completed | May 10, 2026, 5:20 a.m. |
Created at: April 30, 2026, 11:46 p.m.