Triple
T35132954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-American Bowl |
E1014490
|
entity |
| Predicate | hasPositionTypes |
P112307
|
FINISHED |
| Object | 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: offense | Statement: [All-American Bowl, hasPositionTypes, offense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPositionTypes Context triple: [All-American Bowl, hasPositionTypes, offense]
-
A.
hasPositionsFor
Indicates that one entity offers or contains available roles, jobs, or positions for another entity.
-
B.
hasNumberOfTypes
Indicates that an entity is associated with a specific count of distinct types or categories it possesses or includes.
-
C.
hasPPositionDefinition
Indicates that something is associated with or assigned a specific definition of its position or placement.
-
D.
hasPositioning
Indicates that one entity occupies, is arranged in, or is assigned a specific spatial or relative position with respect to another entity or reference frame.
-
E.
typicalPositionType
chosen
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
- 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_69f76dd9c1848190af70d4882a2c1ad7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff48199b1c8190bb05872f8a4f4673 |
completed | May 9, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69ff4746b1cc8190854f70a124df7d04 |
completed | May 9, 2026, 2:40 p.m. |
Created at: May 3, 2026, 4:02 p.m.