Triple
T31853016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volante (uniformed patrol units) |
E813115
|
entity |
| Predicate | dispatchMethod |
P156773
|
FINISHED |
| Object | central police operations room |
—
|
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: central police operations room | Statement: [Volante (uniformed patrol units), dispatchMethod, central police operations room]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dispatchMethod Context triple: [Volante (uniformed patrol units), dispatchMethod, central police operations room]
-
A.
dispatchSystem
chosen
Indicates that a system is responsible for receiving requests and coordinating the assignment and sending of appropriate resources or services to designated targets.
-
B.
implementsMethod
Indicates that one entity provides a concrete implementation of a specified method defined or required elsewhere.
-
C.
switchMethod
Indicates that an entity changes from one method, mode, or procedure to another.
-
D.
triggerMethod
Indicates the method, mechanism, or procedure by which a particular event, action, or process is initiated or triggered.
-
E.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b03f3b148190a1b096da2a6c5864 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:51 p.m.