Triple
T30651222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slow Drag |
E780263
|
entity |
| Predicate | bodyContact |
P169980
|
FINISHED |
| Object | upper body contact |
—
|
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: upper body contact | Statement: [Slow Drag, bodyContact, upper body contact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyContact Context triple: [Slow Drag, bodyContact, upper body contact]
-
A.
ballContactBodyPart
Indicates that a ball is in physical contact with a specific part of a body.
-
B.
bodyContour
Indicates the shape or outline of a body as defined by its external curves and boundaries.
-
C.
targetsBody
Indicates that one entity is directed at, aimed at, or focused on affecting the body of another entity.
-
D.
associatedBody
Indicates a relationship where one entity is linked or connected to another entity as its related or corresponding body.
-
E.
bodyNumber
Indicates the numerical position or identifier assigned to a body within a sequence or collection of bodies.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a98249081909b4be467f5a37110 |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:30 p.m.