Triple
T20425934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waiting for death |
E500999
|
entity |
| Predicate | isConcernOf |
P11116
|
FINISHED |
| Object | 20th-century existential literature |
—
|
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: 20th-century existential literature | Statement: [Waiting for death, isConcernOf, 20th-century existential literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConcernOf Context triple: [Waiting for death, isConcernOf, 20th-century existential literature]
-
A.
concernedSee
Indicates that one entity looks at or observes another with a sense of worry, care, or concern.
-
B.
concernsJurisdiction
Indicates that one entity has legal authority, control, or responsibility over another entity or over matters related to it.
-
C.
targetConcern
Indicates that something is the specific issue, problem, or subject that is the focus of attention, action, or consideration.
-
D.
strategicConcernFor
Indicates a relationship where one entity considers another entity’s situation, actions, or outcomes important for its own long-term goals, risks, or strategic interests.
-
E.
concern
chosen
Indicates that one entity is about, relates to, or is of interest or importance to 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_69e0b4aa68fc8190b1a14c55575ef04a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67ba86ed88190bf2d4448d2abcdc7 |
completed | April 20, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.