Triple
T16930056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baume & Mercier |
E410680
|
entity |
| Predicate | complicationType |
P124789
|
FINISHED |
| Object | chronograph |
—
|
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: chronograph | Statement: [Baume & Mercier, complicationType, chronograph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complicationType Context triple: [Baume & Mercier, complicationType, chronograph]
-
A.
complication
Indicates that one event, action, or condition makes another more difficult, problematic, or introduces an additional obstacle or entanglement in the situation.
-
B.
hasComplication
Indicates that an entity is associated with a problem, difficulty, or adverse outcome arising as a consequence of another condition, action, or process.
-
C.
diseaseType
Indicates that one entity is classified as a specific type or category of disease in relation to another entity.
-
D.
conditions
Indicates that one entity specifies or imposes requirements, constraints, or circumstances that must be satisfied or hold true for another entity or situation.
-
E.
typeOfFaulting
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
- F. None of above. chosen
Provenance (4 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf248c6c81908fbf4d49e5381f08 |
completed | April 18, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.