Triple
T37553924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garr |
E933648
|
entity |
| Predicate | hasBossClassification |
P196728
|
FINISHED |
| Object | raid boss (classic era) |
—
|
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: raid boss (classic era) | Statement: [Garr, hasBossClassification, raid boss (classic era)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBossClassification Context triple: [Garr, hasBossClassification, raid boss (classic era)]
-
A.
hasBossType
Indicates that one entity functions as the superior or boss type in relation to another entity.
-
B.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
-
C.
hasBossForm
chosen
Indicates that an entity has a special, typically more powerful "boss" version or transformation form.
-
D.
isBoss
Indicates that one entity holds a supervisory or managerial authority over another entity in a hierarchical structure.
-
E.
isBossLike
Indicates that one entity behaves in a dominant, authoritative, or leadership manner toward another entity.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4:17 p.m.