Triple
T2102825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strange Meeting |
E37128
|
entity |
| Predicate | publishedPosthumously |
P15628
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Strange Meeting, publishedPosthumously, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publishedPosthumously Context triple: [Strange Meeting, publishedPosthumously, true]
-
A.
publishedAs
Indicates that an entity is released, issued, or made publicly available under a particular name, format, or identity.
-
B.
publishedFor
Indicates that something (such as a work, document, or content) is published with a particular audience, recipient, or target group in mind.
-
C.
isPosthumous
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
D.
isPosthumousWorkOf
chosen
Indicates that a work was created, published, or became known only after the death of the person with whom it is associated.
-
E.
publishedAuthor
Indicates that a person is the author of one or more works that have been formally published.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abbabe1e9081908ea66c5406e2f1d9 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7b7b6288190afa11b4d93bd5666 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.