Triple
T16516093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Alliance |
E401187
|
entity |
| Predicate | onsideKickAlternative |
P123856
|
FINISHED |
| Object | fourth-and-12 conversion 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: fourth-and-12 conversion play | Statement: [The Alliance, onsideKickAlternative, fourth-and-12 conversion play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onsideKickAlternative Context triple: [The Alliance, onsideKickAlternative, fourth-and-12 conversion play]
-
A.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
-
B.
kicker
Indicates that an entity performs the action of kicking another entity, typically in a sports or physical interaction context.
-
C.
A-sideOf
Indicates that one entity is located on or corresponds to the A-side (first or primary side) of another entity, typically in a two-sided context.
-
D.
A-sideWith
Indicates that one entity is aligned or positioned on the same side as another entity.
-
E.
onAlbumSide
Indicates that a particular track or song appears on a specified side (e.g., Side A or Side B) of an album.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e7bbfa481909037148cdb4d8996 |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296995d388190b88ebe189dce890d |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.