Triple
T25873806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reply to the Toast to the Lassies |
E651831
|
entity |
| Predicate | isCustomarily |
P155350
|
FINISHED |
| Object | given after the meal |
—
|
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: given after the meal | Statement: [Reply to the Toast to the Lassies, isCustomarily, given after the meal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCustomarily Context triple: [Reply to the Toast to the Lassies, isCustomarily, given after the meal]
-
A.
customaryEligibility
Indicates that an entity qualifies for something based on established customs, norms, or usual practice rather than formal or exceptional criteria.
-
B.
isPer
Indicates that the subject entity is classified as a person.
-
C.
hasCustomaryAuthority
Indicates that one entity holds traditionally recognized or socially accepted power, control, or decision-making authority over another entity or domain.
-
D.
typicalCustomsStatus
chosen
Indicates the usual or standard customs-related condition or classification that typically applies to an entity or transaction.
-
E.
areRegularIn
Indicates that entities participate in or occur within a context, pattern, or structure in a consistent, uniform, and rule-governed manner.
- 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_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_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:12 a.m.