Triple
T22688399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Critical Push To Talk |
E560979
|
entity |
| Predicate | integrationTarget |
P106650
|
FINISHED |
| Object | land mobile radio systems (in many deployments) |
—
|
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: land mobile radio systems (in many deployments) | Statement: [Mission Critical Push To Talk, integrationTarget, land mobile radio systems (in many deployments)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationTarget Context triple: [Mission Critical Push To Talk, integrationTarget, land mobile radio systems (in many deployments)]
-
A.
integrationGoal
Indicates that one entity has the objective or intended outcome of being combined, unified, or made interoperable with another entity or system.
-
B.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
C.
integrationFeature
chosen
Indicates that one entity provides a capability or component specifically intended to enable or support integration with another system, service, or component.
-
D.
backendTarget
Indicates that one entity serves as the backend system, service, or endpoint that another entity connects to or depends on for processing or functionality.
-
E.
integrationOutcome
Indicates the result or consequence produced when two or more components, systems, or processes are combined or integrated.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178983fc8819080aa00e45ff77952 |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:13 p.m.