Triple
T37707376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Poison |
E939230
|
entity |
| Predicate | convertedUsing |
P65804
|
FINISHED |
| Object | Gunpowder |
—
|
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: Gunpowder | Statement: [Potion of Poison, convertedUsing, Gunpowder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convertedUsing Context triple: [Potion of Poison, convertedUsing, Gunpowder]
-
A.
convertedBy
Indicates that one entity has been transformed or changed in form, state, or representation through the action or process performed by another entity.
-
B.
convertedIn
Indicates that one entity has been transformed, changed, or translated into another form, state, or representation within a specified context.
-
C.
convertedFor
Indicates that one entity has been transformed, adapted, or reformatted specifically for use, compatibility, or suitability with another entity.
-
D.
convertedFrom
Indicates that one entity has been transformed or changed in form, type, or representation from another entity.
-
E.
conversionUse
chosen
Indicates that one entity is used as a means, method, or context for converting another entity from one form, state, or representation to another.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 3, 2026, 4:18 p.m.