Triple
T32865264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johor Circuit |
E840630
|
entity |
| Predicate | hasPrimarySpectatorSport |
P33270
|
FINISHED |
| Object | motorsport |
—
|
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: motorsport | Statement: [Johor Circuit, hasPrimarySpectatorSport, motorsport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimarySpectatorSport Context triple: [Johor Circuit, hasPrimarySpectatorSport, motorsport]
-
A.
hasSportingEvent
Indicates that a sporting event is associated with, held at, or organized by a given entity.
-
B.
hasMajorSport
chosen
Indicates that an entity is associated with or participates in a primary or most prominent sport.
-
C.
hasSportsStatus
Indicates that an entity holds a particular sports-related status, role, or classification (such as amateur, professional, active, or retired) within a sporting context.
-
D.
hasLocalSport
Indicates that a place or community is associated with, supports, or regularly engages in a particular sport at the local level.
-
E.
notableSportIncluded
Indicates that a particular sport is prominently featured or included as a notable component within something, such as an event, program, or context.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0124a5d7848190a6b56d18db2f661d |
completed | May 11, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_6a01243da1808190ada3ce553e3f55b6 |
completed | May 11, 2026, 12:35 a.m. |
Created at: May 1, 2026, 1:17 a.m.