Triple
T14203661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stonehenge replica at Maryhill |
E352027
|
entity |
| Predicate | hasDedicationDate |
P1273
|
FINISHED |
| Object | 1918-07-04 |
—
|
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: 1918-07-04 | Statement: [Stonehenge replica at Maryhill, hasDedicationDate, 1918-07-04]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDedicationDate Context triple: [Stonehenge replica at Maryhill, hasDedicationDate, 1918-07-04]
-
A.
dedicationDate
chosen
Indicates the date on which something (such as a building, monument, or work) is formally dedicated or inaugurated.
-
B.
dedicationStatus
Indicates the current state or condition of an entity’s dedication or commitment, such as whether it is active, pending, completed, or otherwise defined.
-
C.
hasDedicationPurpose
Indicates that something is dedicated, devoted, or assigned to serve a particular purpose or function.
-
D.
dedicationDay
Indicates the date or day on which something, typically a building, monument, or work, is formally dedicated or inaugurated.
-
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_69d827894ac0819097803e57f3227b23 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61f6d4d481909128084e82e6a58a |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:05 a.m.