Triple
T10805103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Víðarr |
E254940
|
entity |
| Predicate | rankAmongGods |
P95551
|
FINISHED |
| Object | one of the strongest Æsir |
—
|
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: one of the strongest Æsir | Statement: [Víðarr, rankAmongGods, one of the strongest Æsir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankAmongGods Context triple: [Víðarr, rankAmongGods, one of the strongest Æsir]
-
A.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
-
B.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
-
C.
protagonistRank
Indicates the relative narrative importance or centrality of a character within a story, typically ranking how primary they are as a protagonist compared to others.
-
D.
peakRanking
Indicates the highest position or rank an entity has ever achieved within a specified ranking system or context.
-
E.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
- F. None of above. chosen
Provenance (4 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d733726e2881908d4fe2cfe046ab43 |
completed | April 9, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:18 p.m.