Triple
T15840151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSV Clubsport |
E384079
|
entity |
| Predicate | relatedModel |
P37
|
FINISHED |
| Object | HSV GTS |
E91023
|
NE 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: HSV GTS | Statement: [HSV Clubsport, relatedModel, HSV GTS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HSV GTS Context triple: [HSV Clubsport, relatedModel, HSV GTS]
-
A.
GTS
chosen
GTS is a high-performance, sport-oriented variant of the Holden Monaro produced by Holden’s performance division.
-
B.
GTS
GTS is an abbreviation commonly used for the Global Telecommunication System, an international network for exchanging meteorological data.
-
C.
HGS
HGS is the National Rail station code assigned to Hastings railway station in East Sussex, England.
-
D.
HVGT
HVGT is the abbreviated name for Hornets Venom GT, the NBA 2K League esports team affiliated with the Charlotte Hornets.
-
E.
HK G3 series
The HK G3 series is a family of 7.62×51mm NATO battle rifles developed in the 1950s that became one of the most widely used and influential military rifles worldwide.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e69360819091ea0556bd66d785 |
completed | April 16, 2026, 8:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa13c931481908ed9fd10fddd867c |
completed | May 9, 2026, 9:03 p.m. |
Created at: April 10, 2026, 4:49 a.m.