Triple
T28001689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Being (Sein) |
E707163
|
entity |
| Predicate | cannotBeGraspedAs |
P167793
|
FINISHED |
| Object | present-at-hand object |
—
|
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: present-at-hand object | Statement: [Being (Sein), cannotBeGraspedAs, present-at-hand object]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBeGraspedAs Context triple: [Being (Sein), cannotBeGraspedAs, present-at-hand object]
-
A.
cannotBeHeldBy
Indicates that one entity is not allowed or not able to possess, carry, or be in control of another entity.
-
B.
canBeHeldWith
Indicates that two entities are compatible or suitable to be held or used together at the same time.
-
C.
canBeHeld
Indicates that an entity is capable of being physically grasped, supported, or carried by another entity.
-
D.
couldHold
Indicates that one entity has the potential capacity or suitability to contain, support, or grasp another entity.
-
E.
canBeHeldIn
Indicates that one entity is capable of being contained, hosted, or conducted within another entity.
- 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_69ef96b980d88190a753b2f9a978595a |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f66cf092c881908d7034c9c2bc61d5 |
completed | May 2, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66c59de9881909ebbb7b0ae7ab495 |
completed | May 2, 2026, 9:27 p.m. |
Created at: April 27, 2026, 7:57 p.m.