Triple
T35010523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. House |
E1009928
|
entity |
| Predicate | keyQuestline |
P85835
|
FINISHED |
| Object | The House Always Wins |
—
|
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 House Always Wins | Statement: [Mr. House, keyQuestline, The House Always Wins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyQuestline Context triple: [Mr. House, keyQuestline, The House Always Wins]
-
A.
questlineAvailableIn
Indicates that a particular questline can be accessed or played within a specified game, mode, or context.
-
B.
centralQuest
chosen
Indicates that an action, objective, or storyline serves as the primary or main quest within a larger narrative or mission structure.
-
C.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
-
D.
objectOfQuest
Indicates that one entity is the target, goal, or item being sought or pursued in another entity’s quest or mission.
-
E.
zoneQuestHub
Indicates a relationship where a particular zone serves as the central hub or main base for quests within a game or system.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.