Triple
T22426116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Nature or On What Is |
E554372
|
entity |
| Predicate | positionOnVoid |
P16734
|
FINISHED |
| Object | denies the existence of void |
—
|
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: denies the existence of void | Statement: [On Nature or On What Is, positionOnVoid, denies the existence of void]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnVoid Context triple: [On Nature or On What Is, positionOnVoid, denies the existence of void]
-
A.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
B.
positionOnGood
chosen
Indicates the stance or viewpoint an entity holds regarding a particular good, such as support, opposition, or neutrality.
-
C.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
D.
positionOnEnvironment
Indicates the spatial placement or location of an entity relative to a surrounding environment or surface.
-
E.
positionOnSubstance
Indicates that one entity is located on the surface of, or supported by, another entity that is treated as a substance or material.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a2d4dd88190a156c24b02b1591b |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.