Triple
T19971620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TT Race Week |
E480088
|
entity |
| Predicate | followsPhase |
P75500
|
FINISHED |
| Object | qualifying and practice week |
—
|
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: qualifying and practice week | Statement: [TT Race Week, followsPhase, qualifying and practice week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsPhase Context triple: [TT Race Week, followsPhase, qualifying and practice week]
-
A.
followOnPhases
chosen
Indicates that certain phases occur subsequently as a continuation or next steps after preceding phases.
-
B.
followsConflictPhase
Indicates that one conflict phase occurs after and is temporally subsequent to another conflict phase.
-
C.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
D.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
E.
followsPass
Indicates that one entity moves behind or in the path of another entity who has just passed, maintaining a trailing or subsequent position.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc9694881909a31841702ab9e5f |
completed | April 20, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.