Triple
T205297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stop TB Partnership |
E4597
|
entity |
| Predicate | advocacyFocus |
P1876
|
FINISHED |
| Object | increased TB funding |
—
|
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: increased TB funding | Statement: [Stop TB Partnership, advocacyFocus, increased TB funding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advocacyFocus Context triple: [Stop TB Partnership, advocacyFocus, increased TB funding]
-
A.
policyFocus
chosen
Indicates that an entity (such as a person, organization, or document) is primarily concerned with, directed toward, or centered on a particular policy area or issue.
-
B.
advocates
Indicates that one entity publicly supports, recommends, or argues in favor of another entity or its interests.
-
C.
ideologicalGoal
Indicates that an entity aims to promote, realize, or advance a particular ideology or set of ideological principles.
-
D.
politicalGoal
Indicates a relationship where an entity aims to achieve, promote, or realize a specific political outcome, policy, or state of affairs.
-
E.
relatedPoliticalProgram
Indicates that one political program is associated with, connected to, or contextually linked with another political program.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25f46b4f081909e5ee3718109a71f |
completed | Feb. 28, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69a25b4b42ec8190bef16bbbdd30a742 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.