Triple
T19956712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greeba |
E479701
|
entity |
| Predicate | isOnRacingLapDistance |
P57550
|
FINISHED |
| Object | approximately 7–8 miles from TT start line at Douglas |
—
|
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: approximately 7–8 miles from TT start line at Douglas | Statement: [Greeba, isOnRacingLapDistance, approximately 7–8 miles from TT start line at Douglas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRacingLapDistance Context triple: [Greeba, isOnRacingLapDistance, approximately 7–8 miles from TT start line at Douglas]
-
A.
distancePerRace
Indicates the total distance covered in a single race event or instance.
-
B.
positionOnLap
Indicates that one entity is physically situated resting on the lap area of another entity.
-
C.
safetyCarLaps
Indicates the number of laps in a race that were completed under safety car conditions.
-
D.
mainTrackDistance
chosen
Indicates the distance measured along the primary or main track between two referenced points or entities.
-
E.
typicalRaceDistanceLaps
Indicates the usual number of laps that constitute the standard race distance for a given racing event or category.
- 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_69e65af08e008190a3a1b807b638a99e |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.