Triple
T29654838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragoon |
E750236
|
entity |
| Predicate | raceTechnology |
P167553
|
FINISHED |
| Object | Khaydarin crystal technology |
—
|
NE NERFINISHED |
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: Khaydarin crystal technology | Statement: [Dragoon, raceTechnology, Khaydarin crystal technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raceTechnology Context triple: [Dragoon, raceTechnology, Khaydarin crystal technology]
-
A.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
-
B.
racingSeries
Indicates that one entity is a racing series in which the other entity (such as a race, team, or driver) participates or to which it belongs.
-
C.
styleOfRacing
Indicates the specific manner or approach in which an entity participates in or performs racing.
-
D.
motorsportClass
Indicates that one entity is classified as a specific motorsport category or division associated with another entity.
-
E.
motorsportDepartment
Indicates that an entity is a department or division responsible for motorsport-related activities within an organization.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f66f269b908190a8a5f65bac23f083 |
completed | May 2, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:54 p.m.