Triple
T29991167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackhammer |
E761881
|
entity |
| Predicate | slamDirection |
P168330
|
FINISHED |
| Object | forward |
—
|
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: forward | Statement: [Jackhammer, slamDirection, forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: slamDirection Context triple: [Jackhammer, slamDirection, forward]
-
A.
scanDirection
Indicates the direction or orientation in which a scanning action is performed or data is acquired.
-
B.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
-
C.
gazeDirection
Indicates the direction in which an entity is looking or focusing its visual attention.
-
D.
directionBy
Indicates that one entity provides directional guidance, orientation, or navigational reference for another entity.
-
E.
isDirection
Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
- 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_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. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 6:38 p.m.