Triple
T8386200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huns |
E197823
|
entity |
| Predicate | peakPowerApproximateDate |
P81787
|
FINISHED |
| Object | c. 440–453 CE |
—
|
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: c. 440–453 CE | Statement: [Huns, peakPowerApproximateDate, c. 440–453 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakPowerApproximateDate Context triple: [Huns, peakPowerApproximateDate, c. 440–453 CE]
-
A.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
B.
originallyReleasedOn
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly available.
-
C.
initialProductionEndDate
Indicates the date on which the initial phase or run of production for something comes to an end.
-
D.
consumerReleaseDate
Indicates the date on which a product or service becomes available for purchase or use by general consumers.
-
E.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80e1bcdc81909111aa33ee996e0a |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76da264881909483b835e1db06da |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 6:02 p.m.