Triple
T20927554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNMIS |
E515384
|
entity |
| Predicate | authorizedMilitaryPersonnel |
P141715
|
FINISHED |
| Object | 10000 |
—
|
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: 10000 | Statement: [UNMIS, authorizedMilitaryPersonnel, 10000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedMilitaryPersonnel Context triple: [UNMIS, authorizedMilitaryPersonnel, 10000]
-
A.
hasMilitaryAuthority
Indicates that one entity possesses formal power or command to direct, control, or make decisions over the military activities or forces of another entity.
-
B.
isMilitaryOfficer
Indicates that the subject holds an official position as an officer within a military organization.
-
C.
hasMilitaryStatus
Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
-
D.
mayBeAwardedToMilitaryPersonnel
Indicates that something (such as an honor, decoration, or benefit) is eligible to be granted to members of the military.
-
E.
militaryPerson
Indicates that the subject is a member of the armed forces or serves in a formal military capacity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e5d53d22d08190bc17ed4bed53804a |
completed | April 20, 2026, 7:26 a.m. |
Created at: April 16, 2026, 12:49 p.m.