Triple
T34797495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Elder Scrolls VI |
E1003130
|
entity |
| Predicate | expectedContent |
P181483
|
FINISHED |
| Object | large explorable world |
—
|
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: large explorable world | Statement: [The Elder Scrolls VI, expectedContent, large explorable world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedContent Context triple: [The Elder Scrolls VI, expectedContent, large explorable world]
-
A.
expectedValue
Indicates the predicted or average outcome of a variable or event, typically computed as a probability-weighted sum of all possible values.
-
B.
holderExpectation
Indicates that one entity has an expectation, belief, or anticipated outcome regarding another entity or situation.
-
C.
expectedAction
Indicates that a particular action is anticipated or required to occur in a given context or scenario.
-
D.
expectedBy
Indicates that one entity is anticipated, required, or relied upon by another as part of a plan, obligation, or dependency.
-
E.
responseExpected
Indicates that a reply, action, or follow-up is anticipated from a specified party in relation to a prior communication or event.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ab085088190ace5734dcc9f1167 |
completed | May 3, 2026, 4:41 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77a39135081908ae22d2a23b44e74 |
completed | May 3, 2026, 4:39 p.m. |
Created at: May 3, 2026, 3:59 p.m.