Triple
T34218609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odin, Vili and Vé |
E877861
|
entity |
| Predicate | gaveToHumans |
P66897
|
FINISHED |
| Object | life and breath |
—
|
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: life and breath | Statement: [Odin, Vili and Vé, gaveToHumans, life and breath]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gaveToHumans Context triple: [Odin, Vili and Vé, gaveToHumans, life and breath]
-
A.
providesToHumans
chosen
Indicates that one entity supplies, furnishes, or makes something available for use or benefit by humans.
-
B.
humanReadable
Indicates that something is expressed in a form that is easily understandable or interpretable by humans.
-
C.
differenceFromHumans
Indicates that something differs from humans in one or more characteristics, behaviors, or properties.
-
D.
isHumanized
Indicates that an entity has been given human characteristics, traits, or form, either literally (made human) or figuratively (anthropomorphized).
-
E.
usedAsNaturalUnitIn
Indicates that something functions as a standard or reference unit for measuring or quantifying another thing within a natural or intrinsic context.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71080959c81909be22e06eb0bc03d |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.