Triple
T38583982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isle of Quel'Danas |
E932304
|
entity |
| Predicate | factionHub |
P168851
|
FINISHED |
| Object | Shattered Sun Offensive |
—
|
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: Shattered Sun Offensive | Statement: [Isle of Quel'Danas, factionHub, Shattered Sun Offensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionHub Context triple: [Isle of Quel'Danas, factionHub, Shattered Sun Offensive]
-
A.
factionFocus
Indicates that an entity is primarily oriented toward, aligned with, or concentrated on a particular faction as its main focus.
-
B.
factionID
Indicates that an entity is associated with, or belongs to, a particular faction identified by a specific ID.
-
C.
factionBase
chosen
Indicates that a particular location serves as the primary base or headquarters for a given faction.
-
D.
factionSystem
Indicates a relationship where a faction is associated with, operates within, or controls a particular system (such as a region, domain, or organizational structure).
-
E.
factionContext
Indicates the broader group, side, or organizational alignment within which an entity’s actions, roles, or relationships take place.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 3, 2026, 4:32 p.m.