Triple
T18179642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appendix Ukraine Scheme |
E435247
|
entity |
| Predicate | isHumanitarianInNature |
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: [Appendix Ukraine Scheme, isHumanitarianInNature, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHumanitarianInNature Context triple: [Appendix Ukraine Scheme, isHumanitarianInNature, 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.
naturalOrHumanCause
Indicates that something results from either natural processes or human activities as its cause.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dff9aad081909cc7eed2b64828f2 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331baeb88190b21f50a98c36c78e |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.