Triple
T25954179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpent Column |
E654050
|
entity |
| Predicate | dateOfOriginalDedication |
P1273
|
FINISHED |
| Object | 5th century BC |
—
|
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: 5th century BC | Statement: [Serpent Column, dateOfOriginalDedication, 5th century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfOriginalDedication Context triple: [Serpent Column, dateOfOriginalDedication, 5th century BC]
-
A.
dedicationDate
chosen
Indicates the date on which something (such as a building, monument, or work) is formally dedicated or inaugurated.
-
B.
dedicationYear
Indicates the year in which something (such as a building, monument, or work) was formally dedicated or consecrated.
-
C.
dedicationDay
Indicates the date or day on which something, typically a building, monument, or work, is formally dedicated or inaugurated.
-
D.
rededicationDate
Indicates the date on which something is formally dedicated again, typically after restoration, change, or renewal.
-
E.
dedicationBy
Indicates that one entity formally dedicates, commits, or devotes another entity (such as a work, resource, or effort) to a particular person, purpose, or cause.
- 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_69e7ab40ac788190a771bc499eb1ae5f |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 22, 2026, 8:44 a.m.