Triple
T6466205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Relief |
E142238
|
entity |
| Predicate | keyFocus |
P64673
|
FINISHED |
| Object | poverty alleviation |
—
|
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: poverty alleviation | Statement: [World Relief, keyFocus, poverty alleviation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyFocus Context triple: [World Relief, keyFocus, poverty alleviation]
-
A.
keyStateFocus
Indicates that a particular key or keyboard input currently has focus or is the active target for input events.
-
B.
keyAction
Indicates an action that is performed using a key, typically involving locking, unlocking, or otherwise operating a mechanism that requires a key.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
keyTarget
Indicates that one entity serves as the primary focus, objective, or intended recipient of another entity’s action, function, or influence.
-
E.
keyThemeIn
chosen
Indicates that a particular theme is a central or primary thematic focus within a given work, context, or subject.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a1159ec81909bbfa9a9d6fa1616 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.