Triple
T14827788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Area Command |
E348618
|
entity |
| Predicate | policeSpeciality |
P90046
|
FINISHED |
| Object | maritime policing |
—
|
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: maritime policing | Statement: [Marine Area Command, policeSpeciality, maritime policing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policeSpeciality Context triple: [Marine Area Command, policeSpeciality, maritime policing]
-
A.
officerCategory
Indicates the classification or type of officer role that an individual holds within an organization or system.
-
B.
policeForceCharacteristic
chosen
Indicates that a specified characteristic, quality, or attribute is associated with a particular police force.
-
C.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
D.
policeCharacter
Indicates that one entity serves as a police officer or law-enforcement figure in relation to another entity.
-
E.
policeDepartmentType
Indicates the specific organizational category or classification of a police department (e.g., municipal, state, federal).
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0737d4c8190a49bf6b013da208c |
completed | April 14, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69de8c13418c819088ff9905ace1416a |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:51 a.m.