Triple
T31483958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hooktail Castle |
E803223
|
entity |
| Predicate | primaryBoss |
P126648
|
FINISHED |
| Object | Hooktail |
E802018
|
NE 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: Hooktail | Statement: [Hooktail Castle, primaryBoss, Hooktail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBoss Context triple: [Hooktail Castle, primaryBoss, Hooktail]
-
A.
optionalBoss
Indicates that one entity may serve as a boss or supervisor of another, but this relationship is not required or always present.
-
B.
finalBossOf
Indicates that one entity serves as the ultimate or last major opponent or challenge that another entity must face or overcome.
-
C.
stageBossOf
chosen
Indicates that one entity serves as the primary boss or main adversary encountered in a particular stage, level, or area associated with another entity.
-
D.
finalBossBefore
Indicates that one entity serves as the final boss encountered immediately before facing the other entity.
-
E.
dropBoss
Indicates that one entity dismisses, removes, or ceases to support another entity who holds a position of authority or leadership.
- F. None of above.
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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b2d73bbec819099ce3d1b20a95ebd |
completed | June 11, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:34 p.m.