Triple
T13426108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rally1 |
E313485
|
entity |
| Predicate | hasHybridBoostDuration |
P109858
|
FINISHED |
| Object | up to 3 seconds |
—
|
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: up to 3 seconds | Statement: [Rally1, hasHybridBoostDuration, up to 3 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHybridBoostDuration Context triple: [Rally1, hasHybridBoostDuration, up to 3 seconds]
-
A.
supportsTurboBoost
Indicates that one entity provides or is compatible with Turbo Boost functionality for another entity or process.
-
B.
usedWithBoosters
Indicates that something is employed or operated in conjunction with boosters to enhance its effect or performance.
-
C.
boosterType
Indicates the specific kind or category of booster associated with an entity or action.
-
D.
hasHybridSpecies
Indicates that one entity is a hybrid species that results from the combination or crossbreeding of another entity (or entities).
-
E.
hasTrailDuration
Indicates that an entity (such as a trail or route) is associated with a specific amount of time required to traverse or complete it.
- F. None of above. chosen
Provenance (4 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed066408190a416880affd8416e |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a0355de48190bb3fb96912e20df3 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:40 p.m.