Triple
T28001688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Being (Sein) |
E707163
|
entity |
| Predicate | groundOf |
P163612
|
FINISHED |
| Object | the intelligibility of beings |
—
|
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: the intelligibility of beings | Statement: [Being (Sein), groundOf, the intelligibility of beings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundOf Context triple: [Being (Sein), groundOf, the intelligibility of beings]
-
A.
immediateSubjectOf
Indicates that one entity is the direct grammatical subject of another entity (typically a clause, phrase, or verb), without any intervening subject relations.
-
B.
locatedUnder
Indicates that one entity is positioned directly or generally beneath another entity in space.
-
C.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
D.
oftenPartOf
Indicates that one entity frequently occurs as a component or subset within another entity, though not necessarily always.
-
E.
usesGroundFor
Indicates that one entity makes functional or practical use of a particular ground, surface, or land area for its activities or purposes.
- 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_69f63bd17884819090b08f0819bebe78 |
completed | May 2, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f63893cc188190883ac9321a95d2dc |
completed | May 2, 2026, 5:46 p.m. |
Created at: April 27, 2026, 7:57 p.m.