Triple
T9115746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Company of Thorin |
E218714
|
entity |
| Predicate | primaryQuest |
P85835
|
FINISHED |
| Object | reclaim the Lonely Mountain |
—
|
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: reclaim the Lonely Mountain | Statement: [Company of Thorin, primaryQuest, reclaim the Lonely Mountain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryQuest Context triple: [Company of Thorin, primaryQuest, reclaim the Lonely Mountain]
-
A.
centralQuest
chosen
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
B.
publicMission
Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
-
C.
primaryTask
Indicates that an entity has a main or most important task, role, or function it is responsible for above all others.
-
D.
primaryIntent
Indicates the main purpose, goal, or motivation underlying an action, event, or relationship among entities.
-
E.
primaryIssue
Indicates that the related item is the main or most important issue among a set of issues.
- 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_69ca83dc94ac8190b9ef42684d36ff39 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a1340881909dc791b825e87ef2 |
completed | April 1, 2026, 5:09 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.