Triple
T37551070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trial of the Crusader |
E933590
|
entity |
| Predicate | successorRaid |
P66717
|
FINISHED |
| Object | Icecrown Citadel |
—
|
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: Icecrown Citadel | Statement: [Trial of the Crusader, successorRaid, Icecrown Citadel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorRaid Context triple: [Trial of the Crusader, successorRaid, Icecrown Citadel]
-
A.
predecessorRaid
Indicates that one raid event occurred immediately before another raid in a sequence or timeline.
-
B.
majorRaid
Indicates a large-scale, coordinated attack or incursion carried out against a target.
-
C.
successorForce
chosen
Indicates that one force or power succeeds, replaces, or takes over the role of another force.
-
D.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
E.
allianceRaidSeries
Indicates that multiple entities participate together as part of the same overarching alliance raid series or campaign.
- 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_6a00af6b3a948190a92813c13384c304 |
completed | May 10, 2026, 4:16 p.m. |
| PD | Predicate disambiguation | batch_6a00aec35610819085dd5137715a4228 |
completed | May 10, 2026, 4:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.