Triple
T14578422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elder Scrolls Online: Gold Road |
E342119
|
entity |
| Predicate | addsFeatureType |
P114930
|
FINISHED |
| Object | new explorable region |
—
|
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: new explorable region | Statement: [The Elder Scrolls Online: Gold Road, addsFeatureType, new explorable region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsFeatureType Context triple: [The Elder Scrolls Online: Gold Road, addsFeatureType, new explorable region]
-
A.
createdFeature
Indicates that one entity brought another entity into existence or caused it to be produced as a feature.
-
B.
setFeature
Indicates assigning or configuring a specific feature or property for an entity.
-
C.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
D.
includesFeatureTypes
Indicates that an entity contains or encompasses specific types of features as part of its composition or definition.
-
E.
registerType
Indicates that an entity is classified or recorded under a specific type or category within a registration system.
- F. None of above. chosen
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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb3f6f78c81908a30ecb4c025299d |
completed | April 14, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69de656a953481909a4645b004c40de7 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:24 a.m.