Triple
T24203746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepsi Plunge |
E600045
|
entity |
| Predicate | landingPositionOfOpponent |
P155178
|
FINISHED |
| Object | face-first on the mat |
—
|
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: face-first on the mat | Statement: [Pepsi Plunge, landingPositionOfOpponent, face-first on the mat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingPositionOfOpponent Context triple: [Pepsi Plunge, landingPositionOfOpponent, face-first on the mat]
-
A.
positionOnOpponents
Indicates that one entity is located on or directly above the opposing side or opponent in a competitive or adversarial context.
-
B.
opposingLocation
Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
-
C.
positionOnTactics
Indicates the stance or viewpoint an entity holds regarding a particular tactic or set of tactics.
-
D.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
E.
ballLocation
Indicates the spatial position or coordinates where a ball is currently located.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca38c148190ae65cd692567d43d |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c9834064819082024233d9c6f98f |
completed | April 29, 2026, 9:04 a.m. |
Created at: April 17, 2026, 11:37 p.m.