Triple
T2341377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navy–Merchant Marine Memorial |
E45033
|
entity |
| Predicate | dateOfDedication |
P1273
|
FINISHED |
| Object | May 30, 1934 |
—
|
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: May 30, 1934 | Statement: [Navy–Merchant Marine Memorial, dateOfDedication, May 30, 1934]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfDedication Context triple: [Navy–Merchant Marine Memorial, dateOfDedication, May 30, 1934]
-
A.
dedicationDate
chosen
Indicates the date on which something (such as a building, monument, or work) is formally dedicated or inaugurated.
-
B.
rededicationDate
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
C.
consecrationDate
Indicates the date on which something (typically a building, object, or person) was formally dedicated or made sacred through a religious or ceremonial act.
-
D.
commemorationDate
Indicates the date on which an event, person, or occasion is formally remembered or honored.
-
E.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.