Triple
T15133357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slip Slide |
E361476
|
entity |
| Predicate | encouragesPlayStyle |
P94746
|
FINISHED |
| Object | aggressive cornering |
—
|
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 cornering | Statement: [Slip Slide, encouragesPlayStyle, aggressive cornering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encouragesPlayStyle Context triple: [Slip Slide, encouragesPlayStyle, aggressive cornering]
-
A.
styleOfPlay
Indicates the characteristic manner or approach in which an entity performs or behaves, especially in a game, sport, or artistic context.
-
B.
encouragesActivities
chosen
Indicates that one entity promotes, supports, or motivates another entity to engage in certain activities.
-
C.
depictedAsEncouraging
Indicates that one entity is portrayed or represented as giving support, confidence, or motivation to another entity.
-
D.
playstyleWeakness
Indicates a relationship where one playstyle is particularly vulnerable or disadvantaged when facing another playstyle.
-
E.
cooperativePlay
Indicates that two or more entities are engaging in a shared, mutually coordinated activity or game toward a common goal.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b29a4c819087f8818e3f5788f5 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.