Triple
T7676732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back Pack Health Worker Team |
E173878
|
entity |
| Predicate | methodOfWork |
P859
|
FINISHED |
| Object | mobile health service delivery |
—
|
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: mobile health service delivery | Statement: [Back Pack Health Worker Team, methodOfWork, mobile health service delivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: methodOfWork Context triple: [Back Pack Health Worker Team, methodOfWork, mobile health service delivery]
-
A.
workBy
Indicates that a work (such as a creation, product, or result) is produced, authored, or created by a particular agent or entity.
-
B.
performsWorkOf
Indicates that one entity carries out, executes, or fulfills the tasks, functions, or role that are normally associated with another entity.
-
C.
worksTo
Indicates that one entity performs work or exerts effort in order to achieve, support, or contribute to another entity or outcome.
-
D.
settingOfWork
Indicates the place, time, or environment in which a creative work’s narrative or events are situated.
-
E.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
- 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_69c6995703e0819081de77361b602e78 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4:01 p.m.