Triple
T20927555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNMIS |
E515384
|
entity |
| Predicate | authorizedCivilianPolice |
P71567
|
FINISHED |
| Object | 715 |
—
|
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: 715 | Statement: [UNMIS, authorizedCivilianPolice, 715]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedCivilianPolice Context triple: [UNMIS, authorizedCivilianPolice, 715]
-
A.
allowsCivilianService
Indicates that an authority permits individuals to perform an alternative form of civilian service instead of regular military service.
-
B.
supportsCivilAuthorities
Indicates that one entity provides assistance, endorsement, or backing to civil authorities in performing their roles or exercising their powers.
-
C.
isCivilianOffice
Indicates that an office or position is non-military and belongs to the civilian sphere of authority or administration.
-
D.
policeControl
chosen
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.
-
E.
civilianEligibility
Indicates that an entity meets the criteria or conditions required to be classified or treated as a civilian in a given 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_69e0b4fb431c8190b9d40e6a72f0cc87 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f652c3188190ace50415b3b30b83 |
completed | April 21, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.