Triple
T29697339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kings of the Swedes |
E751386
|
entity |
| Predicate | notableLegendaryKing |
P73488
|
FINISHED |
| Object | Odin |
E51318
|
NE 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: Odin | Statement: [Kings of the Swedes, notableLegendaryKing, Odin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLegendaryKing Context triple: [Kings of the Swedes, notableLegendaryKing, Odin]
-
A.
notableMythicKing
chosen
Indicates that the subject is recognized as a prominent or distinguished king within myth or legend.
-
B.
notableKingMentionedBySources
Indicates that historical or authoritative sources explicitly mention the king as being notable or significant.
-
C.
notableMonarch
Indicates that the subject is a monarch who is distinguished or historically significant in some notable way.
-
D.
alsoKingOf
Indicates that an entity who is king of one place is simultaneously king of another place as well.
-
E.
kingOf
Indicates that one entity holds the position or role of king in relation to another entity, typically a territory, people, or domain.
- F. None of above.
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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a267ed09f1c8190bb45d816e54a716e |
completed | June 8, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7:21 p.m.