Triple
T14895876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geirröd |
E359873
|
entity |
| Predicate | plansToDo |
P14398
|
FINISHED |
| Object | kill Thor by trickery |
—
|
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: kill Thor by trickery | Statement: [Geirröd, plansToDo, kill Thor by trickery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plansToDo Context triple: [Geirröd, plansToDo, kill Thor by trickery]
-
A.
planner
Indicates that an entity is responsible for organizing, scheduling, or coordinating activities, tasks, or resources.
-
B.
planning
Indicates that an entity is engaged in organizing or devising a future action, event, or course of behavior involving another entity or entities.
-
C.
plan
chosen
Indicates that an entity intends or arranges for a future action or sequence of actions to occur.
-
D.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
E.
planningSkill
Indicates the degree to which an entity is capable of effectively organizing, sequencing, and coordinating actions or resources to achieve goals.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6070b248190be8f4f91a0c0b1f3 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:10 a.m.