Triple
T36518329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Babolat |
E900107
|
entity |
| Predicate | notableStringBrand |
P204913
|
FINISHED |
| Object | Babolat VS |
E900107
|
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: Babolat VS | Statement: [Babolat, notableStringBrand, Babolat VS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStringBrand Context triple: [Babolat, notableStringBrand, Babolat VS]
-
A.
notableBrandElement
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
catalogBrand
Indicates that a brand is associated with, or offered within, a particular catalog.
-
C.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
D.
brandNumber
Indicates the identifying number or code assigned to a particular brand within a system or dataset.
-
E.
brandNameType
Indicates the specific type or category associated with a brand name within a broader branding or naming system.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39dbdded5c819096dbf716e1afddc6 |
completed | June 23, 2026, 1:05 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.