Triple
T2487912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Certainty |
E55971
|
entity |
| Predicate | composedAtEndOf |
P3587
|
FINISHED |
| Object | Ludwig Wittgenstein's life |
—
|
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: Ludwig Wittgenstein's life | Statement: [On Certainty, composedAtEndOf, Ludwig Wittgenstein's life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composedAtEndOf Context triple: [On Certainty, composedAtEndOf, Ludwig Wittgenstein's life]
-
A.
endedWith
chosen
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
B.
concludedAfter
Indicates that one event or process finishes at a time later than the completion of another event or process.
-
C.
assembledNearEndOf
Indicates that one entity is put together or constructed in close proximity to the endpoint or final section of another entity.
-
D.
concludedWith
Indicates that an event, process, or interaction ended or was finalized by a specific outcome, action, or state.
-
E.
composedFor
Indicates that a creative work (typically a piece of music) was specifically written or created for a particular person, group, event, or purpose.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.