Triple
T31851417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busento |
E813074
|
entity |
| Predicate | hasLegendaryEventDate |
P102571
|
FINISHED |
| Object | circa 410 AD (traditional date of Alaric’s burial) |
—
|
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: circa 410 AD (traditional date of Alaric’s burial) | Statement: [Busento, hasLegendaryEventDate, circa 410 AD (traditional date of Alaric’s burial)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendaryEventDate Context triple: [Busento, hasLegendaryEventDate, circa 410 AD (traditional date of Alaric’s burial)]
-
A.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
hasHistoricEventYear
chosen
Indicates the specific year in which a referenced historic event took place.
-
C.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
D.
isHistoricNameOfEventAt
Indicates that a given historic name refers to or was used for a specific event that occurred at a particular place or time.
-
E.
hasLegendaryPlayer
Indicates that an entity (such as a team, club, or organization) is associated with at least one player recognized as legendary.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 30, 2026, 11:51 p.m.