Triple
T1229123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TB REACH |
E26395
|
entity |
| Predicate | focusesOnActivity |
P31
|
FINISHED |
| Object | tuberculosis case detection |
—
|
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: tuberculosis case detection | Statement: [TB REACH, focusesOnActivity, tuberculosis case detection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnActivity Context triple: [TB REACH, focusesOnActivity, tuberculosis case detection]
-
A.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
B.
focusesOnTeam
Indicates that the subject directs attention, effort, or priority toward a particular team as the main area of concern or activity.
-
C.
exportActivity
Indicates an action where goods, services, or data are sent out from one entity or region to another for trade or distribution across borders.
-
D.
activity
Indicates that an entity is engaged in or performing a particular action, behavior, or process.
-
E.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be3dac2c8190914ff27173bb6b34 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.