Triple
T32576359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roosevelt Arch |
E832654
|
entity |
| Predicate | cornerstoneLayingDate |
P174611
|
FINISHED |
| Object | April 24, 1903 |
—
|
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: April 24, 1903 | Statement: [Roosevelt Arch, cornerstoneLayingDate, April 24, 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cornerstoneLayingDate Context triple: [Roosevelt Arch, cornerstoneLayingDate, April 24, 1903]
-
A.
cornerstoneLaidBy
Indicates that the act of laying a building’s cornerstone was performed by a specified agent or entity.
-
B.
datePlannedTempleCornerstonesLaid
Indicates the planned date on which the temple’s cornerstones are scheduled to be laid.
-
C.
dateOfCanonicalErection
Indicates the official date on which an institution, organization, or entity was formally and canonically established or erected according to relevant legal or religious norms.
-
D.
reErectedAt
Indicates that something was rebuilt or re-erected at a particular location or site.
-
E.
constructionDate
Indicates the date on which an entity (such as a building or structure) was constructed or completed.
- F. None of above. chosen
Provenance (4 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c63f57188190a67c787135fad0a4 |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c2df27ec8190912ec8eb488836d0 |
completed | May 3, 2026, 3:37 a.m. |
Created at: May 1, 2026, 1:04 a.m.