Triple
T26654874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations-coordinated aid program |
E666467
|
entity |
| Predicate | providesAidTo |
P55302
|
FINISHED |
| Object | Skopje |
—
|
NE NERFINISHED |
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: Skopje | Statement: [United Nations-coordinated aid program, providesAidTo, Skopje]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesAidTo Context triple: [United Nations-coordinated aid program, providesAidTo, Skopje]
-
A.
hasReliefEffortFrom
Indicates that a party receives assistance or support through a relief effort provided by another party.
-
B.
rescuesWith
Indicates that one entity saves or frees another entity from danger, harm, or captivity using a particular means, tool, or method.
-
C.
rescuesFrom
Indicates that one entity saves or frees another entity from a dangerous, harmful, or undesirable situation or source.
-
D.
seeksToRescue
Indicates an entity’s intention or effort to save or free another entity from danger, harm, or an undesirable situation.
-
E.
offeredAid
chosen
Indicates that one entity provided or proposed help, support, or resources to another entity.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 27, 2026, 2:34 a.m.