Triple
T20657178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Division Memorial |
E507656
|
entity |
| Predicate | rededicated |
P3370
|
FINISHED |
| Object | 1962 |
—
|
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: 1962 | Statement: [Second Division Memorial, rededicated, 1962]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rededicated Context triple: [Second Division Memorial, rededicated, 1962]
-
A.
rededicatedBy
Indicates that something has been dedicated again or anew by a particular agent or entity.
-
B.
laterRededicatedTo
Indicates that something was originally dedicated to one purpose or entity and, at a later time, was dedicated again to a different purpose or entity.
-
C.
dedicated
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
D.
rededicationDate
chosen
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
E.
recommissioned
Indicates that something previously deactivated, retired, or out of service has been restored and formally returned to active use or operation.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ee049081909904efe2dc683cd5 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.