Triple
T17043883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama Law Enforcement Radio System |
E413513
|
entity |
| Predicate | interoperabilityScope |
P114886
|
FINISHED |
| Object | inter-agency |
—
|
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: inter-agency | Statement: [Alabama Law Enforcement Radio System, interoperabilityScope, inter-agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interoperabilityScope Context triple: [Alabama Law Enforcement Radio System, interoperabilityScope, inter-agency]
-
A.
interoperabilityWith
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
B.
interoperabilityStandard
Indicates that there is a standard or specification enabling different systems, components, or technologies to work together and exchange information seamlessly.
-
C.
standardizationScope
Indicates the extent or domain within which a standard or standardization effort is intended to apply or be enforced.
-
D.
collaborationScope
chosen
Indicates the extent, boundaries, and areas of responsibility covered by a particular collaboration between entities.
-
E.
operationalScope
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9c112c81908232dc6908d831cf |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.