Triple
T32509387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pip the Troll |
E830886
|
entity |
| Predicate | transformedIntoTrollBy |
P85351
|
FINISHED |
| Object | mutagenic ale |
—
|
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: mutagenic ale | Statement: [Pip the Troll, transformedIntoTrollBy, mutagenic ale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transformedIntoTrollBy Context triple: [Pip the Troll, transformedIntoTrollBy, mutagenic ale]
-
A.
wasTransformedBy
chosen
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
-
B.
motherTransformedInto
Indicates that an entity’s mother has been changed or converted into another form, state, or entity.
-
C.
turnedVillainBecause
Indicates that an entity became a villain as a result of another entity’s actions, influence, or circumstances associated with that other entity.
-
D.
turnsIntoAnimals
Indicates a transformation relationship where an entity changes its form or state into one or more animals.
-
E.
bodyTransformedInto
Indicates that one entity’s physical form is changed or converted into another specified form or entity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1 a.m.