Triple
T34162023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lóðurr (in some scholarly theories) |
E876302
|
entity |
| Predicate | proposedIdentificationWith |
P61935
|
FINISHED |
| Object | Loki |
—
|
NE NERFINISHED |
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: Loki | Statement: [Lóðurr (in some scholarly theories), proposedIdentificationWith, Loki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedIdentificationWith Context triple: [Lóðurr (in some scholarly theories), proposedIdentificationWith, Loki]
-
A.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
B.
possibleIdentificationProposedByScholars
chosen
Indicates that scholars have proposed a possible identification of one entity with another, without asserting it as certain.
-
C.
alternativeIdentification
Indicates that one entity serves as an alternative identifier or reference for another entity.
-
D.
candidateIdentifiedAs
Indicates that a particular individual or option has been recognized or designated as the specific candidate in question.
-
E.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 1, 2026, 1:54 a.m.