Triple
T35156275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XT 300 |
E1015128
|
entity |
| Predicate | designedToCompeteIn |
P109551
|
FINISHED |
| Object | Fiorano GT Challenge seasons |
—
|
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: Fiorano GT Challenge seasons | Statement: [XT 300, designedToCompeteIn, Fiorano GT Challenge seasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToCompeteIn Context triple: [XT 300, designedToCompeteIn, Fiorano GT Challenge seasons]
-
A.
designedForCompetition
chosen
Indicates that something was intentionally created or configured to be used in a competitive context or event.
-
B.
competeIn
Indicates that an entity takes part as a contender in a particular event, activity, or domain where performance is compared against others.
-
C.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
D.
tieneCompetenciaEn
Indicates that an entity possesses skill, expertise, or competence in a specific area, field, or activity.
-
E.
usesCompetition
Indicates that one entity employs or leverages another entity as a competitor or within a competitive 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff0d80c0dc81909fbd12285c7a45c0 |
completed | May 9, 2026, 10:33 a.m. |
| PD | Predicate disambiguation | batch_69ff0cd03e78819094895058f925fbfa |
completed | May 9, 2026, 10:30 a.m. |
Created at: May 3, 2026, 4:02 p.m.