Triple
T20189871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hylians |
E492954
|
entity |
| Predicate | originInLore |
P40749
|
FINISHED |
| Object | descendants of the goddess Hylia’s chosen people |
—
|
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: descendants of the goddess Hylia’s chosen people | Statement: [Hylians, originInLore, descendants of the goddess Hylia’s chosen people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originInLore Context triple: [Hylians, originInLore, descendants of the goddess Hylia’s chosen people]
-
A.
originMyth
chosen
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
-
B.
originOfCharacter
Indicates the source or place from which a character originates or is created.
-
C.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
-
D.
describesOriginOf
Indicates that one entity specifies or explains the source, provenance, or origin of another entity.
-
E.
characterOrigin
Indicates the source, background, or initial context from which a character originates.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad4d7a88190b70dfb74a2daafba |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.