Triple
T34989329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shady Sands region |
E1009336
|
entity |
| Predicate | conflictInLore |
P182471
|
FINISHED |
| Object | raider attacks on early Shady Sands settlements |
—
|
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: raider attacks on early Shady Sands settlements | Statement: [Shady Sands region, conflictInLore, raider attacks on early Shady Sands settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictInLore Context triple: [Shady Sands region, conflictInLore, raider attacks on early Shady Sands settlements]
-
A.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
conflictDescribedIn
Indicates that a particular conflict is documented, detailed, or discussed within a specified information source or description.
-
C.
conflictIntroduced
Indicates that a conflict has been newly created or brought into existence between the related entities.
-
D.
conflictHistory
Indicates a history of conflict or antagonistic interactions that have occurred between the related entities.
-
E.
conflictsInvolvedIn
Indicates that an entity participates as a party or actor in one or more conflicts.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78dbf72648190a4971a558e9d1889 |
completed | May 3, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78ce43094819093857fc99f269afe |
completed | May 3, 2026, 5:59 p.m. |
Created at: May 3, 2026, 4:01 p.m.