Triple
T34218605
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Odin, Vili and Vé |
E877861
|
entity |
| Predicate | createdHumansFrom |
P178012
|
FINISHED |
| Object | ash tree |
—
|
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: ash tree | Statement: [Odin, Vili and Vé, createdHumansFrom, ash tree]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdHumansFrom Context triple: [Odin, Vili and Vé, createdHumansFrom, ash tree]
-
A.
createdBeingFrom
chosen
Indicates that one entity brought another entity into existence or produced it as a result of its creative action.
-
B.
creatorOfInhabitants
Indicates that an entity is the creator or originator of the beings or inhabitants of another entity (such as a place, world, or domain).
-
C.
creationResult
Indicates that one entity is the outcome or product that comes into existence as a result of another entity’s act of creation.
-
D.
createdLukeFrom
Indicates that one entity brought another entity, specifically Luke, into existence or originated him from something.
-
E.
createdForFamilyOf
Indicates that something was created or produced specifically for the benefit, use, or needs of a particular family or family group.
- 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_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: May 1, 2026, 1:55 a.m.