Triple
T4586365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Onchan, Isle of Man |
E101976
|
entity |
| Predicate | hasMotorSportFeature |
P8241
|
FINISHED |
| Object | TT course section |
—
|
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: TT course section | Statement: [Onchan, Isle of Man, hasMotorSportFeature, TT course section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotorSportFeature Context triple: [Onchan, Isle of Man, hasMotorSportFeature, TT course section]
-
A.
supportsDrivetrainFeature
Indicates that an entity provides or is compatible with a specified drivetrain-related capability or function.
-
B.
hasMotorsportInvolvement
chosen
Indicates that an entity is involved in motorsport, such as through participation, organization, sponsorship, or other direct association with motor racing activities.
-
C.
hasMountingFeature
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
D.
hasRacecourseFeature
Indicates that something possesses or includes a specific feature or characteristic related to a racecourse.
-
E.
hasParkFeature
Indicates that a park includes, contains, or is associated with a specific feature or amenity.
- 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_69bd43d4ce208190b53158c882b222e3 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5906a43c81908fb11bf8f94be122 |
completed | March 20, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69bd522acbcc8190bf24d9517793a2c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.