Triple
T37472391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darkhaven |
E931184
|
entity |
| Predicate | questFunction |
P183780
|
FINISHED |
| Object | starting point for multiple Revendreth quest chains |
—
|
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: starting point for multiple Revendreth quest chains | Statement: [Darkhaven, questFunction, starting point for multiple Revendreth quest chains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questFunction Context triple: [Darkhaven, questFunction, starting point for multiple Revendreth quest chains]
-
A.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
-
B.
questlineFeature
chosen
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
C.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
-
D.
questContent
Indicates that one entity is the content, objective, or narrative substance of a quest associated with another entity.
-
E.
questLocationFor
Indicates that a particular location is the place where a given quest occurs, is based, or must be undertaken.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:17 p.m.