Triple
T34989666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Aldmeri Dominion |
E1009344
|
entity |
| Predicate | temporarilyInfluences |
P173356
|
FINISHED |
| Object | Black Marsh |
—
|
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: Black Marsh | Statement: [Second Aldmeri Dominion, temporarilyInfluences, Black Marsh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporarilyInfluences Context triple: [Second Aldmeri Dominion, temporarilyInfluences, Black Marsh]
-
A.
influencedByCurrent
Indicates that something’s state, behavior, or outcome is affected or determined by the current conditions, context, or situation.
-
B.
temporalEffect
Indicates a relationship where one event, state, or action produces consequences or changes that occur at a later time.
-
C.
influenceOf
chosen
Indicates that one entity affects, shapes, or alters the state, behavior, or properties of another entity.
-
D.
temporarilyBecomes
Indicates that one entity changes into or assumes the state, role, or form of another entity for a limited period of time before reverting or changing again.
-
E.
influencedIn
Indicates that one entity had an effect on or shaped another entity within a specific context, domain, or setting.
- 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_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:01 p.m.