Triple
T8327943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNMIL |
E195000
|
entity |
| Predicate | authorizedPolicePersonnelCeiling |
P23274
|
FINISHED |
| Object | 1115 |
—
|
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: 1115 | Statement: [UNMIL, authorizedPolicePersonnelCeiling, 1115]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedPolicePersonnelCeiling Context triple: [UNMIL, authorizedPolicePersonnelCeiling, 1115]
-
A.
maximumAuthorizedPolicePersonnel
chosen
Indicates the highest number of police personnel that are officially permitted or authorized for a given jurisdiction, unit, or context.
-
B.
lawEnforcementLevel
Indicates the degree or intensity of law enforcement presence, activity, or strictness applied in a given context.
-
C.
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.
-
D.
policePresence
Indicates that law enforcement officers are present at or monitoring a particular location, event, or situation.
-
E.
officersAre
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f8243288190b1ae74d69395fc91 |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:56 p.m.