Triple
T35013277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | southwestern Tamriel |
E1009987
|
entity |
| Predicate | includesHomeland |
P2102
|
FINISHED |
| Object | Valenwood |
E308895
|
NE 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: Valenwood | Statement: [southwestern Tamriel, includesHomeland, Valenwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesHomeland Context triple: [southwestern Tamriel, includesHomeland, Valenwood]
-
A.
exampleHomeland
Indicates that a location serves as the native land or place of origin associated with an entity.
-
B.
homelandFeature
Indicates that a particular geographic or environmental feature is characteristic of, located in, or strongly associated with an entity’s homeland.
-
C.
hasHomeland
chosen
Indicates that an entity considers or recognizes a particular place or region as its homeland or place of origin.
-
D.
wasHomelandIn
Indicates that a location historically served as the homeland or place of origin for a specified group or entity.
-
E.
viewOfHomeland
Indicates a perspective, opinion, or emotional attitude that an entity holds toward its homeland.
- F. None of above.
Provenance (4 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a387262e2848190828f2a0d91104809 |
completed | June 21, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.