Triple
T29991168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackhammer |
E761881
|
entity |
| Predicate | landingPosition |
P124736
|
FINISHED |
| Object | opponent back-first on 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: opponent back-first on mat | Statement: [Jackhammer, landingPosition, opponent back-first on mat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingPosition Context triple: [Jackhammer, landingPosition, opponent back-first on mat]
-
A.
landingConfiguration
chosen
Indicates the specific arrangement or setup used for an entity’s landing phase or landing operation.
-
B.
landing
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
C.
landingArea
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
-
D.
landingRequires
Indicates that performing a landing action is contingent upon satisfying a specified requirement or precondition.
-
E.
landingPilot
Indicates that an entity is acting as the pilot responsible for landing an aircraft or spacecraft.
- 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_69f224695498819094a81037cad401e2 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6791aa82c8190afb7c808cddbf46a |
completed | May 2, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:38 p.m.