Triple
T19398051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TACC |
E485243
|
entity |
| Predicate | increasesSpeedWhen |
P3962
|
FINISHED |
| Object | traffic ahead speeds up and road is clear |
—
|
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: traffic ahead speeds up and road is clear | Statement: [TACC, increasesSpeedWhen, traffic ahead speeds up and road is clear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: increasesSpeedWhen Context triple: [TACC, increasesSpeedWhen, traffic ahead speeds up and road is clear]
-
A.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
-
B.
accelerates
chosen
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
-
C.
increasedRateOn
Indicates that one entity has raised the rate, fee, or charge applied to another entity.
-
D.
speed
Indicates the rate at which an entity moves or changes position over time.
-
E.
speedAchieved
Indicates that a particular speed has been reached or attained by an entity during an event or action.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62574edd08190b5456108d5e3907e |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.