Triple
T25002092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nothing But Nets |
E625740
|
entity |
| Predicate | measuresSuccessBy |
P35854
|
FINISHED |
| Object | number of bed nets distributed |
—
|
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: number of bed nets distributed | Statement: [Nothing But Nets, measuresSuccessBy, number of bed nets distributed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: measuresSuccessBy Context triple: [Nothing But Nets, measuresSuccessBy, number of bed nets distributed]
-
A.
successMetric
chosen
Indicates the specific criterion or measure used to evaluate whether an action, process, or relationship has achieved its intended success.
-
B.
succeedsBy
Indicates that one entity comes after or replaces another in a sequence, order, or position.
-
C.
measuredBy
Indicates that something’s quantity, extent, or value is determined or expressed using a particular measurement method, instrument, or unit.
-
D.
isSuccessful
Indicates that an action, process, or attempt has achieved its intended goal or outcome.
-
E.
denotesSuccess
Indicates that an action, process, or operation has achieved its intended goal or outcome successfully.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b0bf1a081908b202efe0fcb73cf |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.