Triple
T11144431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ents |
E263634
|
entity |
| Predicate | originInLegendarium |
P90611
|
FINISHED |
| Object | requested by Yavanna |
—
|
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: requested by Yavanna | Statement: [Ents, originInLegendarium, requested by Yavanna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originInLegendarium Context triple: [Ents, originInLegendarium, requested by Yavanna]
-
A.
legendarium
chosen
Indicates a relationship where a work, element, or concept belongs to, is part of, or is defined within a particular fictional legendarium or mythic narrative universe.
-
B.
originMyth
Indicates the traditional myth or legendary narrative that explains the beginnings or creation of a people, place, institution, or phenomenon.
-
C.
originOfCharacter
Indicates the source or place from which a character originates or is created.
-
D.
roleInLegendarium
Indicates that one entity serves a particular narrative or functional role within the fictional mythos or legendarium associated with 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8634d5481909b114d30a542ea3f |
completed | April 9, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.