Triple
T26387365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run and shoot offense |
E663317
|
entity |
| Predicate | primaryFormationType |
P36931
|
FINISHED |
| Object | spread offense |
—
|
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: spread offense | Statement: [Run and shoot offense, primaryFormationType, spread offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFormationType Context triple: [Run and shoot offense, primaryFormationType, spread offense]
-
A.
primaryFormation
chosen
Indicates that one entity serves as the main or original formation or structural configuration associated with another entity.
-
B.
stateOfFormation
Indicates the jurisdiction or region in which an entity was legally created or organized.
-
C.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
D.
formationType
Indicates the specific structural or organizational configuration in which something is arranged, created, or formed.
-
E.
primaryMoundType
Indicates the main or dominant type of mound associated with or characterizing an entity.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 26, 2026, 11:23 p.m.