Triple
T31989714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canik TP9 series |
E816829
|
entity |
| Predicate | hasCompetitionVariant |
P204214
|
FINISHED |
| Object | Canik TP9 SFx |
E1986060
|
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: Canik TP9 SFx | Statement: [Canik TP9 series, hasCompetitionVariant, Canik TP9 SFx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetitionVariant Context triple: [Canik TP9 series, hasCompetitionVariant, Canik TP9 SFx]
-
A.
hasCompetitionElement
Indicates that one entity includes, involves, or is associated with a specific competitive component, aspect, or feature.
-
B.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
C.
hasCompetitionContext
Indicates that an entity is associated with or occurs within a specific competitive setting, event, or environment.
-
D.
tieneCompetencia
Indicates that one entity has or faces competition from another entity.
-
E.
hasCompetitionUse
Indicates that something is used or intended to be used in a competitive context, such as in contests, tournaments, or rivalrous activities.
- F. None of above. chosen
Provenance (5 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a034af7066c81908719bff353d77b16 |
completed | May 12, 2026, 3:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3485e8ce748190ae2623cdd2e9a7a4 |
completed | June 18, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_6a034a2fc2308190b0b8fbd458a39323 |
completed | May 12, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_6a034af656d88190881820908f6d2958 |
completed | May 12, 2026, 3:44 p.m. |
Created at: May 1, 2026, 12:13 a.m.