Triple
T28001676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Being (Sein) |
E707163
|
entity |
| Predicate | disclosedThrough |
P87910
|
FINISHED |
| Object | Dasein’s being-in-the-world |
—
|
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: Dasein’s being-in-the-world | Statement: [Being (Sein), disclosedThrough, Dasein’s being-in-the-world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disclosedThrough Context triple: [Being (Sein), disclosedThrough, Dasein’s being-in-the-world]
-
A.
discloses
Indicates that one entity reveals, makes known, or provides previously non-public information to another entity or to the public.
-
B.
exposedThrough
chosen
Indicates that something becomes revealed, accessible, or affected as a result of passing through or being subjected to another thing or medium.
-
C.
coversDisclosureOf
Indicates that one entity’s scope, terms, or provisions include and apply to the act or content of another entity’s disclosure.
-
D.
typeOfDisclosure
Indicates the specific category or nature of a disclosure made in a given context (e.g., legal, financial, personal).
-
E.
disclosureLevel
Indicates the extent or degree to which information is revealed, shared, or made accessible in a given context.
- 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_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. |
Created at: April 27, 2026, 7:57 p.m.