Triple
T35051295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stros M'Kai |
E1011334
|
entity |
| Predicate | hasQuestHubIn |
P183546
|
FINISHED |
| Object | The Elder Scrolls Online |
—
|
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: The Elder Scrolls Online | Statement: [Stros M'Kai, hasQuestHubIn, The Elder Scrolls Online]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuestHubIn Context triple: [Stros M'Kai, hasQuestHubIn, The Elder Scrolls Online]
-
A.
hasQuestHubRole
Indicates that an entity holds a specific role or function within a quest hub context.
-
B.
hasQuestContentIn
Indicates that a quest’s narrative or objectives are contained within or associated with a particular location, context, or container.
-
C.
hasQuestElement
Indicates that something is a component, step, or requirement that forms part of a larger quest or mission.
-
D.
hasMissionIn
Indicates that an entity carries out, undertakes, or is assigned a mission within a specified location or region.
-
E.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
- 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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:01 p.m.