Triple
T38589998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkandi, Greatsword of the Brotherhood |
E932430
|
entity |
| Predicate | hasHighTopEndDamage |
P201209
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ashkandi, Greatsword of the Brotherhood, hasHighTopEndDamage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighTopEndDamage Context triple: [Ashkandi, Greatsword of the Brotherhood, hasHighTopEndDamage, true]
-
A.
hasBurstDamagePotential
Indicates the extent to which an entity can inflict a large amount of damage in a short, concentrated period of time.
-
B.
hasTopness
Indicates that an entity possesses the quantum property of topness, typically associated with the presence or contribution of a top quark.
-
C.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
D.
hasTopConstruction
Indicates that one entity serves as the uppermost structural element or construction positioned on top of another entity.
-
E.
hasTypeOfDamage
Indicates that an entity experiences or exhibits a specific kind or category of damage.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
| PDg | Predicate description generation | batch_69ffde916fcc81908d6e1b4e6d3f761c |
completed | May 10, 2026, 1:25 a.m. |
Created at: May 3, 2026, 4:32 p.m.