Triple
T284645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romulus Augustulus |
E5861
|
entity |
| Predicate | depositionDate |
P9118
|
FINISHED |
| Object | 4 September 476 |
—
|
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: 4 September 476 | Statement: [Romulus Augustulus, depositionDate, 4 September 476]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: depositionDate Context triple: [Romulus Augustulus, depositionDate, 4 September 476]
-
A.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
-
B.
decisionDate
Indicates the date on which a specific decision was formally made or finalized.
-
C.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
-
D.
legalDepositSince
Indicates that a legal deposit obligation or status has been in effect for the subject entity continuously since the specified date.
-
E.
dateSigned
Indicates the specific date on which an agreement, document, or contract was formally signed.
- 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c4b773c81908f1017f40b0bfd07 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.