Triple
T7187264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American football |
E167602
|
entity |
| Predicate | commonPlayType |
P29019
|
FINISHED |
| Object | running play |
—
|
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: running play | Statement: [American football, commonPlayType, running play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonPlayType Context triple: [American football, commonPlayType, running play]
-
A.
playType
chosen
Indicates the specific category or style of play or performance associated with an event or action.
-
B.
canAlsoBePlayedIn
Indicates that something (such as a game, media, or activity) is additionally playable or usable in another context, format, or environment beyond its primary one.
-
C.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
D.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
E.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e2506881909fc4e81b9b79e873 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.