Triple
T25954181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serpent Column |
E654050
|
entity |
| Predicate | dateOfRelocation |
P39457
|
FINISHED |
| Object | 4th century AD |
—
|
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: 4th century AD | Statement: [Serpent Column, dateOfRelocation, 4th century AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfRelocation Context triple: [Serpent Column, dateOfRelocation, 4th century AD]
-
A.
relocationYear
Indicates the year in which an entity was moved or transferred from one location to another.
-
B.
headquartersMovedOn
Indicates that the location of an entity’s headquarters changed on a specific date or point in time.
-
C.
relocatedDuring
chosen
Indicates that an entity changed its location or place of residence within the time span of a specified event or period.
-
D.
dateOfTransfer
Indicates the specific date on which a transfer of something (such as ownership, rights, or funds) from one party to another takes place.
-
E.
relocationOpeningDate
Indicates the date on which a relocation (such as a move or transfer to a new place) is officially opened or becomes effective.
- 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_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 22, 2026, 8:44 a.m.