Triple
T25873765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toast to the Lassies |
E651830
|
entity |
| Predicate | isCustomarilyDeliveredAfter |
P159372
|
FINISHED |
| Object | Immortal Memory |
—
|
NE NERFINISHED |
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: Immortal Memory | Statement: [Toast to the Lassies, isCustomarilyDeliveredAfter, Immortal Memory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCustomarilyDeliveredAfter Context triple: [Toast to the Lassies, isCustomarilyDeliveredAfter, Immortal Memory]
-
A.
mustBeDeliveredBy
Indicates that one entity is required to be delivered or completed no later than a specified time, date, or deadline set by another entity.
-
B.
deliveredAt
Indicates the specific time or location at which something (such as a message, product, or service) is delivered.
-
C.
deliveredDuring
Indicates that one entity was delivered within the time span defined by another entity or temporal interval.
-
D.
firstDeliveryDate
Indicates the date on which an item, service, or order is delivered for the first time.
-
E.
typicalDelivery
Indicates the usual or standard way in which something is delivered, reflecting the most common delivery method or pattern in that context.
- F. None of above. chosen
Provenance (4 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_69e7ab3ad9d88190841ddcb93ab02e96 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f602dea1388190a5e8567388c2838a |
completed | May 2, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 8:12 a.m.