Triple
T26346720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolling Thunder |
E662793
|
entity |
| Predicate | requiresAthleticism |
P110078
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rolling Thunder, requiresAthleticism, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresAthleticism Context triple: [Rolling Thunder, requiresAthleticism, yes]
-
A.
hasAthleticLevel
Indicates the degree or category of athletic ability, fitness, or performance associated with an entity.
-
B.
isAthletic
chosen
Indicates that an entity possesses physical fitness, strength, agility, or endurance characteristic of athletic ability.
-
C.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
D.
physicallyConditionedAs
Indicates that one entity has been brought into or exists in a particular physical state or condition as specified by another entity or descriptor.
-
E.
isAthlete
Indicates that an entity participates in sports or athletic activities, typically at a competitive or professional level.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 26, 2026, 10:42 p.m.