Triple
T35734895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballon Bleu watch collection |
E1032860
|
entity |
| Predicate | hasMovementOption |
P23273
|
FINISHED |
| Object | automatic mechanical movement |
—
|
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: automatic mechanical movement | Statement: [Ballon Bleu watch collection, hasMovementOption, automatic mechanical movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMovementOption Context triple: [Ballon Bleu watch collection, hasMovementOption, automatic mechanical movement]
-
A.
hasMovementVariant
Indicates that one movement is an alternative or variant form of another movement.
-
B.
hasMovementLegacy
Indicates that an entity carries forward, preserves, or significantly influences the ongoing impact, traditions, or ideals of a particular movement.
-
C.
haveMovementFor
Indicates that an entity exhibits or is assigned a specific type or pattern of movement in relation to another entity or context.
-
D.
hasMovementCharacter
Indicates that an entity exhibits a particular style, quality, or pattern of movement.
-
E.
hasMovementType
chosen
Indicates the type or mode of movement associated with an entity, such as how it moves or is transported.
- 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_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.