Triple
T37554424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hydraxian Waterlords |
E933660
|
entity |
| Predicate | questHubNPC |
P192110
|
FINISHED |
| Object | Duke Hydraxis |
—
|
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: Duke Hydraxis | Statement: [Hydraxian Waterlords, questHubNPC, Duke Hydraxis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questHubNPC Context triple: [Hydraxian Waterlords, questHubNPC, Duke Hydraxis]
-
A.
questGiverIn
Indicates that an entity serves as the quest giver within a specified quest, location, or context.
-
B.
questlineFeature
Indicates that something is a notable element, step, or component within a larger questline or narrative progression.
-
C.
questLocationFor
Indicates that a particular location is the place where a given quest occurs, is based, or must be undertaken.
-
D.
questHubFor
Indicates a relationship where one entity serves as the central location or main coordination point for quests associated with another entity.
-
E.
questContent
Indicates that one entity is the content, objective, or narrative substance of a quest associated with another 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:17 p.m.