Triple
T13044376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Foot Police |
E327278
|
entity |
| Predicate | policingType |
P7908
|
FINISHED |
| Object | military police |
—
|
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: military police | Statement: [Military Foot Police, policingType, military police]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policingType Context triple: [Military Foot Police, policingType, military police]
-
A.
policingModel
Indicates the approach, strategy, or framework used to organize and conduct policing activities or law enforcement operations.
-
B.
policeDepartmentType
Indicates the specific organizational category or classification of a police department (e.g., municipal, state, federal).
-
C.
policeSystem
Indicates a relationship where an entity functions as, belongs to, or is governed by a system of law enforcement or policing.
-
D.
typeOfLawEnforcement
chosen
Indicates that one entity is a specific kind or category of law enforcement associated with another entity.
-
E.
policeControl
Indicates that one entity exercises authoritative oversight, regulation, or enforcement power over another, as a police force does over people or areas under its jurisdiction.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:56 p.m.