Triple
T4689793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCG vaccine |
E104005
|
entity |
| Predicate | globalUse |
P11850
|
FINISHED |
| Object | one of the most widely used vaccines worldwide |
—
|
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: one of the most widely used vaccines worldwide | Statement: [BCG vaccine, globalUse, one of the most widely used vaccines worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalUse Context triple: [BCG vaccine, globalUse, one of the most widely used vaccines worldwide]
-
A.
usedWorldwide
chosen
Indicates that something is utilized or applied across many countries or regions around the world.
-
B.
globalResponse
Indicates a reaction, policy, or set of actions taken collectively at an international or worldwide level in response to a particular event or situation.
-
C.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
D.
usedAcross
Indicates that something is utilized or applied in multiple different contexts, locations, or domains.
-
E.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd66059bfc8190885d26d05dd38df1 |
completed | March 20, 2026, 3:21 p.m. |
| PD | Predicate disambiguation | batch_69bd6219da948190bbbb50f08573ab4d |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:16 p.m.