Triple
T15264856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super GT |
E364871
|
entity |
| Predicate | alsoRacesOutsideCountry |
P117877
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Super GT, alsoRacesOutsideCountry, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoRacesOutsideCountry Context triple: [Super GT, alsoRacesOutsideCountry, Yes]
-
A.
alsoRacedOn
Indicates that two entities participated as competitors in at least one of the same races or racing events.
-
B.
playedInCountryWithDifferentRules
Indicates that an entity participated in an activity or event in a country where the rules governing that activity differ from those in the entity’s usual or original context.
-
C.
alsoInCountry
Indicates that something located in one country is additionally located or present in another specified country.
-
D.
hasRaceWalkingEvents
Indicates that the subject includes or features race walking events as part of its activities or program.
-
E.
otherGrandTour
Indicates a relationship where an entity participates in or is associated with a Grand Tour event that is not the primary or main one under consideration.
- F. None of above. chosen
Provenance (4 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00851c5b88190a296b6a105d3ee30 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.