Triple
T37981746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok watch factory |
E947567
|
entity |
| Predicate | watchModel |
P189821
|
FINISHED |
| Object | Vostok Komandirskie |
—
|
NE NERFINISHED |
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: Vostok Komandirskie | Statement: [Vostok watch factory, watchModel, Vostok Komandirskie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: watchModel Context triple: [Vostok watch factory, watchModel, Vostok Komandirskie]
-
A.
watchMovementType
Indicates the type of mechanical or electronic movement mechanism that drives how a watch operates.
-
B.
watches
Indicates that one entity observes or views another entity or event, typically by looking at it attentively over a period of time.
-
C.
watchesVia
Indicates that one entity views or consumes content through a particular medium, platform, or device.
-
D.
watchmaking
Indicates the action or process of designing, assembling, and adjusting watches or timekeeping mechanisms.
-
E.
chronometerNumber
Indicates that an entity has been assigned a specific chronometer identification number, linking it to that unique timekeeping device record.
- 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_69f76ef8a1d08190a741bbbc5970e3b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc993caa881908c16c3e21efaeef9 |
completed | May 6, 2026, 11:07 p.m. |
Created at: May 3, 2026, 4:20 p.m.