Triple
T6350933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End TB Strategy |
E142867
|
entity |
| Predicate | baselineYear |
P68415
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [End TB Strategy, baselineYear, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baselineYear Context triple: [End TB Strategy, baselineYear, 2015]
-
A.
banYear
Indicates the year in which a ban was enacted or came into effect on the related entity or activity.
-
B.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
C.
yearOfReference
chosen
Indicates the specific year to which a statement, measurement, or data point is intended to apply or be interpreted with reference.
-
D.
deprecatedYear
Indicates the year in which something (such as a feature, standard, or item) was officially marked as deprecated or no longer recommended for use.
-
E.
year
Indicates the specific calendar year associated with an entity, event, or fact.
- 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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067dc2790819084aaf7067dc25733 |
completed | March 22, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69c060ec091c8190912aac44e1b8b1c9 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.