Triple
T28533546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Positioning System satellites |
E722101
|
entity |
| Predicate | atomicClockType |
P17358
|
FINISHED |
| Object | cesium atomic clock |
—
|
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: cesium atomic clock | Statement: [Global Positioning System satellites, atomicClockType, cesium atomic clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atomicClockType Context triple: [Global Positioning System satellites, atomicClockType, cesium atomic clock]
-
A.
clockType
chosen
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
B.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
C.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
D.
hasClockMaker
Indicates that an entity has, is associated with, or was created/maintained by a specific clock maker.
-
E.
timeSystem
Indicates a relationship where an entity uses, follows, or is defined within a particular system for measuring or organizing time.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64fd847008190b2e0f3364ac3fedd |
completed | May 2, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:30 a.m.