Triple
T37714044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fury MAX |
E939411
|
entity |
| Predicate | hasRelativePower |
P122913
|
FINISHED |
| Object | higher than standard MAX models |
—
|
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: higher than standard MAX models | Statement: [Fury MAX, hasRelativePower, higher than standard MAX models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativePower Context triple: [Fury MAX, hasRelativePower, higher than standard MAX models]
-
A.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
-
B.
hasAssociatedPower
Indicates that one entity possesses, is linked to, or is characterized by a particular power or capability.
-
C.
hasPowerSimilarTo
Indicates that one entity possesses a level or type of power comparable to that of another entity.
-
D.
powerRangeRelativeTo
chosen
Indicates the comparative span or limits of power one entity has relative to another entity or reference standard.
-
E.
hasPowerful
Indicates that one entity possesses significant strength, influence, or capability relative to another entity or context.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.