Triple
T35734897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballon Bleu watch collection |
E1032860
|
entity |
| Predicate | hasComplicationOption |
P183616
|
FINISHED |
| Object | date display |
—
|
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: date display | Statement: [Ballon Bleu watch collection, hasComplicationOption, date display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComplicationOption Context triple: [Ballon Bleu watch collection, hasComplicationOption, date display]
-
A.
hasComplication
Indicates that an entity is associated with a problem, difficulty, or adverse outcome arising as a consequence of another condition, action, or process.
-
B.
complicationAvailable
chosen
Indicates that a complication (an additional, often optional feature or module) is present and can be used or applied in the given context.
-
C.
hasResolutionOption
Indicates that an entity offers or is associated with one or more selectable resolution settings or choices.
-
D.
hasMaterialOption
Indicates that an entity can be made from, or is available in, one or more alternative materials.
-
E.
complicationType
Indicates the specific kind or category of complication associated with an event, condition, or process.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.