Triple
T3883505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House on Fire |
E92880
|
entity |
| Predicate | documentsAchievement |
P9672
|
FINISHED |
| Object | eradication of smallpox |
—
|
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: eradication of smallpox | Statement: [House on Fire, documentsAchievement, eradication of smallpox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsAchievement Context triple: [House on Fire, documentsAchievement, eradication of smallpox]
-
A.
achievementDefinition
Indicates that one entity specifies or defines the criteria, properties, or structure of an achievement associated with another entity.
-
B.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
C.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
-
D.
documentsDecisionsOn
Indicates that one entity records, details, or formally captures the decisions made about another entity.
-
E.
associatedAchievement
chosen
Indicates a relationship where one entity is linked to, or recognized in connection with, a particular achievement.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec9029908190a7b36a3827734db1 |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.