Triple
T27777956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sekonda |
E699251
|
entity |
| Predicate | timepieceType |
P48663
|
FINISHED |
| Object | quartz watches |
—
|
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: quartz watches | Statement: [Sekonda, timepieceType, quartz watches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timepieceType Context triple: [Sekonda, timepieceType, quartz watches]
-
A.
watchMovementType
chosen
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.
chronometerNumber
Indicates that an entity has been assigned a specific chronometer identification number, linking it to that unique timekeeping device record.
-
D.
watchmaking
Indicates the action or process of designing, assembling, and adjusting watches or timekeeping mechanisms.
-
E.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 5:07 p.m.