Triple
T38585547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highmaul |
E932336
|
entity |
| Predicate | mythicRaidSize |
P191228
|
FINISHED |
| Object | 20 players |
—
|
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: 20 players | Statement: [Highmaul, mythicRaidSize, 20 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mythicRaidSize Context triple: [Highmaul, mythicRaidSize, 20 players]
-
A.
majorRaid
Indicates a large-scale, coordinated attack or incursion carried out against a target.
-
B.
mythicAlliance
Indicates a cooperative or strategic partnership formed between entities within a legendary, mythical, or supernatural context.
-
C.
mythicAction
Indicates an action or event characterized by legendary, supernatural, or culturally mythologized qualities within a narrative or symbolic context.
-
D.
mythicReputation
Indicates a reputation or renown of legendary, larger-than-life status associated with an entity.
-
E.
raidBossIn
Indicates that an entity serves as or is designated as the raid boss within a specified raid, instance, or location.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdaa2bfc08190beccabb0f1782d0d |
completed | May 7, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:32 p.m.