Triple
T34365529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Run Run |
E881998
|
entity |
| Predicate | featuresEnergeticStyle |
P25796
|
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: [Run Run, featuresEnergeticStyle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresEnergeticStyle Context triple: [Run Run, featuresEnergeticStyle, true]
-
A.
featuresAggressiveProductionStyle
Indicates that the subject’s production is characterized by intense, forceful, or hard-hitting stylistic choices.
-
B.
playstyleBenefit
Indicates that one playstyle provides an advantage, improvement, or positive effect to a player or entity.
-
C.
fashionCharacteristic
Indicates a relationship where one entity possesses or exhibits a particular style, trend, or fashion-related attribute in relation to another.
-
D.
featuresStyle
chosen
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
-
E.
clothingFeature
Indicates that one entity has a specific clothing-related attribute, detail, or characteristic associated with 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a031c6c728c81909c1d010048df71c3 |
completed | May 12, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_6a031bfc3b74819098c551096b1fcf00 |
completed | May 12, 2026, 12:24 p.m. |
Created at: May 1, 2026, 1:58 a.m.