Triple
T25954275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obelisk of Theodosius |
E654052
|
entity |
| Predicate | reErectionDate |
P126333
|
FINISHED |
| Object | AD 390 |
—
|
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: AD 390 | Statement: [Obelisk of Theodosius, reErectionDate, AD 390]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reErectionDate Context triple: [Obelisk of Theodosius, reErectionDate, AD 390]
-
A.
canonicalErectionDate
Indicates the officially recognized date on which something (typically a structure, institution, or entity) was formally established or erected.
-
B.
reerectionDate
chosen
Indicates the date on which something that was previously removed, dismantled, or taken down is erected or put back up again.
-
C.
reReleaseDate
Indicates the date on which something is released again, such as a reissued or updated version of an existing item.
-
D.
reErectedAt
Indicates that something was rebuilt or re-erected at a particular location or site.
-
E.
inceptionDate
Indicates the date on which an entity, event, or relationship was first created, established, or began to exist.
- 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_69f6049a5508819085be78ba6fbbfd69 |
completed | May 2, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:44 a.m.