Triple
T24021534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruthless |
E594835
|
entity |
| Predicate | characterizesStyle |
P144821
|
FINISHED |
| Object | aggressive fighting style |
—
|
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: aggressive fighting style | Statement: [Ruthless, characterizesStyle, aggressive fighting style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterizesStyle Context triple: [Ruthless, characterizesStyle, aggressive fighting style]
-
A.
styleCharacter
chosen
Indicates that one entity defines, influences, or characterizes the stylistic qualities or manner of expression of another entity.
-
B.
characterStyle
Indicates how a character is visually or typographically presented, such as its font, weight, size, or decorative attributes.
-
C.
hasStyleCharacteristics
Indicates that one entity exhibits or embodies the stylistic features, traits, or qualities associated with another entity.
-
D.
styleTendsTo
Indicates that one style is generally inclined or likely to develop, appear, or be adopted in the direction of another style.
-
E.
styleDescribedAs
Indicates that the manner, aesthetic, or mode of something is characterized or labeled using a particular style description.
- 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_69e288be2c288190a3a46006945557f7 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5aaf8588190b266557d573504b8 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:50 p.m.