Triple
T787092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House on Fire: The Fight to Eradicate Smallpox |
E16826
|
entity |
| Predicate | describesMethod |
P16102
|
FINISHED |
| Object | ring vaccination |
—
|
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: ring vaccination | Statement: [House on Fire: The Fight to Eradicate Smallpox, describesMethod, ring vaccination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describesMethod Context triple: [House on Fire: The Fight to Eradicate Smallpox, describesMethod, ring vaccination]
-
A.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
B.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
C.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
D.
notableMethod
chosen
Indicates that a particular method, technique, or approach is especially significant, recognized, or noteworthy in relation to the associated entity.
-
E.
hasDescription
Indicates that an entity is associated with a textual description that explains or characterizes it.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a78171908190a38a70274bfbebf9 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50db97c8190a1c55673f4a357b4 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.