Triple
T37028269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby (gemstone) |
E916415
|
entity |
| Predicate | traditionalAnniversary |
P143924
|
FINISHED |
| Object | 40th wedding anniversary |
—
|
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: 40th wedding anniversary | Statement: [Ruby (gemstone), traditionalAnniversary, 40th wedding anniversary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalAnniversary Context triple: [Ruby (gemstone), traditionalAnniversary, 40th wedding anniversary]
-
A.
anniversaryOf
Indicates that one event or date marks the commemoration or yearly recurrence of another specific event.
-
B.
typeOfAnniversary
Indicates the specific category or kind of anniversary that an event or date represents (e.g., wedding, work, founding).
-
C.
anniversaryNumber
Indicates the specific ordinal count of an anniversary occurrence in a recurring commemorative event or relationship.
-
D.
associatedWithAnniversary
chosen
Indicates a relationship where something is connected or related to an anniversary event, date, or celebration.
-
E.
signedOnAnniversaryOf
Indicates that an agreement or document was signed on the anniversary date of a specific prior event or reference point.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:14 p.m.