Triple
T36555380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Stone Troll |
E901684
|
entity |
| Predicate | describedTrollBehavior |
P183170
|
FINISHED |
| Object | bone-chewing |
—
|
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: bone-chewing | Statement: [The Stone Troll, describedTrollBehavior, bone-chewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedTrollBehavior Context triple: [The Stone Troll, describedTrollBehavior, bone-chewing]
-
A.
behaviorDescription
chosen
Indicates a textual explanation or characterization of how an entity behaves or acts in a given context.
-
B.
depictsBehavior
Indicates that one entity visually represents or portrays the behavior or actions of another entity.
-
C.
behaviorTowardGru
Indicates how an entity acts or conducts itself in relation to Gru.
-
D.
frequentlyTaunts
Indicates that one entity repeatedly mocks, provokes, or ridicules another entity on a regular or frequent basis.
-
E.
describesContemptAs
Indicates that one entity characterizes or portrays another entity or subject in terms of contempt.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 4:11 p.m.