Triple
T38643602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Firelands |
E938662
|
entity |
| Predicate | supportsRaidFinder |
P206596
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Firelands, supportsRaidFinder, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsRaidFinder Context triple: [Firelands, supportsRaidFinder, false]
-
A.
hasRaid
Indicates that an entity is associated with, participates in, or is the target of a raid event or operation.
-
B.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
-
C.
raidID
Indicates a unique identifier that associates entities with a specific raid event or operation.
-
D.
raidSizeSupport
Indicates the extent to which one entity supports, enables, or is compatible with a particular RAID configuration size.
-
E.
supportsFinding
Indicates that one entity provides the capability or functionality needed to perform, enable, or carry out a particular finding operation on another entity or resource.
- 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_69f76ed948ec81908ce7811608a8f359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.