Triple
T6803813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMSA SportsCar Championship |
E156249
|
entity |
| Predicate | featuresParticipants |
P2434
|
FINISHED |
| Object | professional racing teams |
—
|
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: professional racing teams | Statement: [IMSA SportsCar Championship, featuresParticipants, professional racing teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresParticipants Context triple: [IMSA SportsCar Championship, featuresParticipants, professional racing teams]
-
A.
eventParticipant
Indicates that an entity takes part in, is involved in, or participates in a particular event.
-
B.
featuresEvent
Indicates that an entity includes, presents, or highlights a particular event as part of its content or offering.
-
C.
participantFrom
Indicates that a participant originates from, is associated with, or comes out of a specified source, group, or context.
-
D.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
E.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
- 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e8d7888190a837620967a150e3 |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.