Triple
T33048952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunnic Empire |
E845672
|
entity |
| Predicate | heightOfPower |
P36248
|
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: [Hunnic Empire, heightOfPower, c. 440–453 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heightOfPower Context triple: [Hunnic Empire, heightOfPower, c. 440–453 CE]
-
A.
heightAboveSurroundings
Indicates that an entity’s vertical position or elevation is higher than that of its immediate surrounding area.
-
B.
powerLevel
chosen
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
C.
heightDescription
Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
-
D.
powersAscentOf
Indicates that one entity provides the driving force, energy, or enabling influence behind another entity’s rise, advancement, or upward progression.
-
E.
heightAboveGround
Indicates the vertical distance of an entity measured from the ground surface directly beneath it.
- 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_69f3495242e48190996a2cb2beab5455 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:24 a.m.