Triple
T8722202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fumble (1978 NFL play) |
E207037
|
entity |
| Predicate | turnoverType |
P84273
|
FINISHED |
| Object | fumble |
—
|
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: fumble | Statement: [The Fumble (1978 NFL play), turnoverType, fumble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnoverType Context triple: [The Fumble (1978 NFL play), turnoverType, fumble]
-
A.
transferType
Indicates the specific method or category of how something is transferred from one entity to another.
-
B.
typeOfReorganization
Indicates the specific kind or category of organizational restructuring that is being or has been carried out.
-
C.
rosterTurnover
Indicates a change in the members of a group or team, such as additions, removals, or replacements within its roster.
-
D.
inversionType
Indicates the specific kind or category of inversion relationship that holds between entities, such as one being the reverse, opposite, or role-swapped form of the other.
-
E.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d0609f48190adc56226724b16c6 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc489dd528819084ed5d88bd8bb3d6 |
completed | March 31, 2026, 10:20 p.m. |
Created at: March 30, 2026, 6:36 p.m.