Triple
T28001549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The History of Beyng |
E707160
|
entity |
| Predicate | marksStageIn |
P79945
|
FINISHED |
| Object | Heidegger’s post–Being and Time thought |
—
|
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: Heidegger’s post–Being and Time thought | Statement: [The History of Beyng, marksStageIn, Heidegger’s post–Being and Time thought]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksStageIn Context triple: [The History of Beyng, marksStageIn, Heidegger’s post–Being and Time thought]
-
A.
marksPhase
chosen
Indicates that one event, state, or condition designates the beginning, end, or boundary of a particular phase in a process or sequence.
-
B.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
C.
marksStatus
Indicates that one entity assigns, records, or updates the status or condition of another entity.
-
D.
marksBoundaryIn
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
-
E.
marksDetermine
Indicates that one entity’s marks or scores determine or decisively influence the outcome, status, or classification of another entity.
- 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_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 7:57 p.m.