Triple
T28518896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calla Bryn Sturgis |
E721701
|
entity |
| Predicate | raidsOccurEvery |
P164607
|
FINISHED |
| Object | approximately 23 years |
—
|
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: approximately 23 years | Statement: [Calla Bryn Sturgis, raidsOccurEvery, approximately 23 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidsOccurEvery Context triple: [Calla Bryn Sturgis, raidsOccurEvery, approximately 23 years]
-
A.
raidingPattern
Indicates a recurring or characteristic way in which raids are planned, organized, or carried out between entities.
-
B.
dateOfMajorRaid
Indicates the specific calendar date on which a major raid event took place.
-
C.
majorRaid
Indicates a large-scale, coordinated attack or incursion carried out against a target.
-
D.
hasRaid
Indicates that an entity is associated with, participates in, or is the target of a raid event or operation.
-
E.
associatedRaid
Indicates a relationship where one entity is linked to or involved with a particular raid event or operation.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fa087648190abaf756ae4e8375c |
completed | May 2, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 3:19 a.m.