Triple
T16961588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monographs programme |
E411443
|
entity |
| Predicate | reportsUsedFor |
P125396
|
FINISHED |
| Object | cancer prevention |
—
|
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: cancer prevention | Statement: [Monographs programme, reportsUsedFor, cancer prevention]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportsUsedFor Context triple: [Monographs programme, reportsUsedFor, cancer prevention]
-
A.
reportsUsedBy
Indicates that a report is utilized or referenced by another entity (such as a user, system, or process).
-
B.
reportsImplementedBy
Indicates that a report is realized, produced, or carried out by a specific implementing entity or system.
-
C.
reportsFor
Indicates that one entity is subordinate to another and is required to provide updates or answer to that entity, typically within an organizational or hierarchical structure.
-
D.
reportsWithin
Indicates that one entity submits or delivers a report to another entity within a specified time frame or boundary.
-
E.
reportsThrough
Indicates that one entity formally communicates and is accountable to another entity through an established reporting or supervisory chain.
- F. None of above. chosen
Provenance (4 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0209a9081909d9c62456bc16e14 |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.