Triple
T126844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Communications Division |
E2568
|
entity |
| Predicate | typeOfService |
P849
|
FINISHED |
| Object | emergency communications support |
—
|
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: emergency communications support | Statement: [Emergency Communications Division, typeOfService, emergency communications support]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfService Context triple: [Emergency Communications Division, typeOfService, emergency communications support]
-
A.
hasServiceType
chosen
Indicates that an entity is associated with or categorized by a particular type of service.
-
B.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
C.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
typeOfWork
Indicates the kind or category of work associated with or performed by an 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a25761e9248190a7205bfc36cb5c45 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.