Triple
T154131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Polio Eradication Initiative |
E3140
|
entity |
| Predicate | usesIntervention |
P7702
|
FINISHED |
| Object | oral polio vaccine |
—
|
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: oral polio vaccine | Statement: [Global Polio Eradication Initiative, usesIntervention, oral polio vaccine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIntervention Context triple: [Global Polio Eradication Initiative, usesIntervention, oral polio vaccine]
-
A.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
B.
integrates
Indicates that one entity combines or brings together another entity or set of entities into a unified, functioning whole.
-
C.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
D.
usedWith
Indicates that one entity is typically or appropriately employed together with another entity in a combined or complementary use.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to another entity.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258e0b11c8190b7b5cf3c354c47ce |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2565c727c8190bca9ba6ca52f216a |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a258de46888190835db2b21a093eaa |
completed | Feb. 28, 2026, 2:54 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.