Triple
T28533545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Positioning System satellites |
E722101
|
entity |
| Predicate | carryPayload |
P124266
|
FINISHED |
| Object | atomic clocks |
—
|
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: atomic clocks | Statement: [Global Positioning System satellites, carryPayload, atomic clocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carryPayload Context triple: [Global Positioning System satellites, carryPayload, atomic clocks]
-
A.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
-
B.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
C.
externalPayloadCapacity
Indicates the maximum weight of payload that can be carried externally (outside the main body or cargo area) by an entity.
-
D.
cargoLoading
Indicates the action or process of placing cargo onto a vehicle, vessel, or other transport medium for shipment or movement.
-
E.
cargoContents
chosen
Indicates that one entity contains or carries another entity as its cargo.
- 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.