Triple
T1229066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STBP |
E26393
|
entity |
| Predicate | problemAddressed |
P3847
|
FINISHED |
| Object | tuberculosis as a public health problem |
—
|
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 as a public health problem | Statement: [STBP, problemAddressed, tuberculosis as a public health problem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: problemAddressed Context triple: [STBP, problemAddressed, tuberculosis as a public health problem]
-
A.
problemStatement
Indicates that an entity presents, defines, or expresses a specific problem or issue to be addressed.
-
B.
addressesIssue
chosen
Indicates that one entity deals with, responds to, or attempts to resolve a specific issue associated with another entity.
-
C.
problems
Indicates that one entity has issues, difficulties, or complications associated with or caused by another entity.
-
D.
aimsToSolve
Indicates an intention or purpose directed toward resolving, addressing, or eliminating a particular problem, challenge, or issue.
-
E.
underlyingIssue
Indicates that one situation, problem, or condition is the fundamental cause or root problem behind another.
- 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.