Triple
T6935996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lament for the Makaris |
E160554
|
entity |
| Predicate | reflectsConcernWith |
P11116
|
FINISHED |
| Object | personal mortality |
—
|
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: personal mortality | Statement: [Lament for the Makaris, reflectsConcernWith, personal mortality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsConcernWith Context triple: [Lament for the Makaris, reflectsConcernWith, personal mortality]
-
A.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
B.
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.
-
C.
concernsClause
Indicates that one entity (such as a document, statement, or discussion) is about, relates to, or addresses a particular clause.
-
D.
targetConcern
Indicates that something is the specific issue, problem, or subject that is the focus of attention, action, or consideration.
-
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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:27 p.m.