Triple
T16919400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega SA |
E410404
|
entity |
| Predicate | officialTimekeeperSince |
P124719
|
FINISHED |
| Object | 1932 |
—
|
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: 1932 | Statement: [Omega SA, officialTimekeeperSince, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialTimekeeperSince Context triple: [Omega SA, officialTimekeeperSince, 1932]
-
A.
knownSince
Indicates the point in time from which one entity has been aware of, acquainted with, or in possession of knowledge about another entity.
-
B.
titleHolderSince
Indicates the entity that has held a particular title or position continuously from a specified starting time.
-
C.
representedSince
Indicates that one entity has been acting as a representative or agent for another entity continuously from a specified starting time.
-
D.
hasClockMaker
Indicates that an entity has, is associated with, or was created/maintained by a specific clock maker.
-
E.
usedAsOfficialTime
Indicates that something is employed as the recognized standard or authoritative reference for measuring time in an official context.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cded2f8481909a20cc08b47e922e |
completed | April 18, 2026, 6:31 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.