Triple
T34989951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Y’ffre |
E1009350
|
entity |
| Predicate | homeRegionInLore |
P70557
|
FINISHED |
| Object | Valenwood |
—
|
NE NERFINISHED |
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: Valenwood | Statement: [Y’ffre, homeRegionInLore, Valenwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeRegionInLore Context triple: [Y’ffre, homeRegionInLore, Valenwood]
-
A.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
B.
culturalRegionOfLore
Indicates that a particular cultural region is the primary setting, origin, or contextual background for a given body of lore or tradition.
-
C.
homeCountryRegion
Indicates the country or broader geographic region that is considered the primary home or origin of an entity.
-
D.
landingRegion
Indicates the area or zone where an object or entity comes to rest or makes contact after moving or descending.
-
E.
homelandRegion
chosen
Indicates that a region is recognized as the native or traditional homeland of a particular entity (such as a people, group, or organization).
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.