Triple
T26387195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valdosta State Blazers football (offensive coordinator) |
E663312
|
entity |
| Predicate | typicalScheme |
P166656
|
FINISHED |
| Object | pass-oriented 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: pass-oriented offense | Statement: [Valdosta State Blazers football (offensive coordinator), typicalScheme, pass-oriented offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalScheme Context triple: [Valdosta State Blazers football (offensive coordinator), typicalScheme, pass-oriented offense]
-
A.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
B.
schemeType
chosen
Indicates the classification or category of a scheme that an entity is associated with or operates under.
-
C.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
D.
notableScheme
Indicates that an entity is particularly recognized or prominent within a specific scheme, system, or organizational framework.
-
E.
typicalDesignation
Indicates that one entity is the usual or commonly used designation (name, label, or title) for another 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_69fe91383a1c81909266e40c3c3ede6c |
completed | May 9, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69fe8fde094081908f0f121664fbb5c7 |
completed | May 9, 2026, 1:37 a.m. |
Created at: April 26, 2026, 11:23 p.m.