Triple
T5441564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 75th Anniversary of the Battle of Gettysburg reunion |
E122145
|
entity |
| Predicate | hasAnniversaryNumber |
P8485
|
FINISHED |
| Object | 75 |
—
|
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: 75 | Statement: [75th Anniversary of the Battle of Gettysburg reunion, hasAnniversaryNumber, 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnniversaryNumber Context triple: [75th Anniversary of the Battle of Gettysburg reunion, hasAnniversaryNumber, 75]
-
A.
anniversaryNumber
chosen
Indicates the specific ordinal count of an anniversary occurrence in a recurring commemorative event or relationship.
-
B.
typeOfAnniversary
Indicates the specific category or kind of anniversary that an event or date represents (e.g., wedding, work, founding).
-
C.
signedOnAnniversaryOf
Indicates that an agreement or document was signed on the anniversary date of a specific prior event or reference point.
-
D.
awardedOnAnniversaryTo
Indicates that something is given as an award to a recipient specifically on the occasion of an anniversary.
-
E.
completionAnniversary
Indicates the date or event marking the anniversary of when something was originally completed.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.