Triple
T9663726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Emergency Unit |
E233649
|
entity |
| Predicate | isHumanitarian |
P43054
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Military Emergency Unit, isHumanitarian, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHumanitarian Context triple: [Military Emergency Unit, isHumanitarian, true]
-
A.
hasHumanitarianAspect
chosen
Indicates that something involves, relates to, or has implications for humanitarian concerns such as human welfare, relief, or the protection of human rights.
-
B.
hasHumanitarianPresence
Indicates that a humanitarian organization or effort is present and actively operating in relation to the referenced entity.
-
C.
humanitarianCrisis
Indicates a situation in which a population faces severe, widespread threats to life, health, or basic living conditions that require urgent humanitarian assistance.
-
D.
isHuman
Indicates that the subject entity possesses the defining characteristics or status of being a human.
-
E.
isPhilanthropic
Indicates that an entity habitually engages in generous actions or donations intended to promote the welfare of others.
- 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_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c0cde048190b5a8e1548825d4d9 |
completed | April 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b3239c8190b3ae3b9bd121e4bd |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:14 p.m.