Triple
T36555408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Stone Troll |
E901684
|
entity |
| Predicate | containsConflict |
P129294
|
FINISHED |
| Object | hobbit versus troll over a bone |
—
|
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: hobbit versus troll over a bone | Statement: [The Stone Troll, containsConflict, hobbit versus troll over a bone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsConflict Context triple: [The Stone Troll, containsConflict, hobbit versus troll over a bone]
-
A.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
B.
linkedConflict
Indicates a relationship where one conflict is directly associated with, related to, or dependent on another conflict.
-
C.
hasConflictStatus
Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
-
D.
triggersConflict
Indicates that one entity initiates or causes a dispute, clash, or incompatibility to arise with another entity or within a system.
-
E.
conflictsOccurIn
chosen
Indicates that one or more conflicts take place within, or are situated in, a specified context, location, or setting.
- 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_6a013a251b4081908b43d85dd95586c5 |
completed | May 11, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_6a0137e4ea988190812173a5ff044098 |
completed | May 11, 2026, 1:59 a.m. |
Created at: May 3, 2026, 4:11 p.m.