Triple
T11174457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Týr |
E264371
|
entity |
| Predicate | hasParentAccordingToSource |
P98256
|
FINISHED |
| Object | Odin in some traditions |
—
|
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: Odin in some traditions | Statement: [Týr, hasParentAccordingToSource, Odin in some traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentAccordingToSource Context triple: [Týr, hasParentAccordingToSource, Odin in some traditions]
-
A.
hasParentExchange
Indicates that one entity is associated with, or belongs to, a higher-level or originating exchange entity that acts as its parent in an exchange hierarchy.
-
B.
hasNotableParent
Indicates that an entity has a parent who is distinguished, prominent, or otherwise notable.
-
C.
hasParentSeries
Indicates that a work or item belongs to, or is derived from, a broader parent series.
-
D.
hasParentMaterial
Indicates that one entity is derived from, formed in, or directly associated with another entity that serves as its original or underlying material.
-
E.
hasParentSIG
Indicates that an entity is the biological or legal parent of another entity within the SIG context.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e897774c819088ebc7231cebfba6 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
| PDg | Predicate description generation | batch_69d7706116248190a87440bec3960884 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:29 p.m.