Triple
T37873966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Enclave |
E944671
|
entity |
| Predicate | oppositeFactionArea |
P195333
|
FINISHED |
| Object | Sunreaver's Sanctuary |
—
|
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: Sunreaver's Sanctuary | Statement: [Silver Enclave, oppositeFactionArea, Sunreaver's Sanctuary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oppositeFactionArea Context triple: [Silver Enclave, oppositeFactionArea, Sunreaver's Sanctuary]
-
A.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
B.
opposingUnits
Indicates that two units are in opposition to each other, such as being on rival sides, conflicting forces, or competing entities within a given context.
-
C.
opponentForceAllegiance
Indicates that one force, group, or individual is aligned with or belongs to an opposing or enemy side in a conflict or competition.
-
D.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
E.
opposingLocation
Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
| PDg | Predicate description generation | batch_69fdbaa1313081908beea28a5597ae40 |
completed | May 8, 2026, 10:27 a.m. |
Created at: May 3, 2026, 4:19 p.m.