Triple
T28533510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Positioning System satellites |
E722101
|
entity |
| Predicate | initialBlock |
P171791
|
FINISHED |
| Object | Block I |
—
|
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: Block I | Statement: [Global Positioning System satellites, initialBlock, Block I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialBlock Context triple: [Global Positioning System satellites, initialBlock, Block I]
-
A.
firstBlockHeight
Indicates the vertical size or elevation of the initial block in a sequence or structure.
-
B.
firstBlockMessage
Indicates that this is the initial message sent in the context of a blocking action or block-related interaction between entities.
-
C.
initialBlockReward
Indicates the reward amount granted for mining or validating the very first block in a blockchain or similar system.
-
D.
firstBlockReward
Indicates the initial reward amount granted for producing or validating the very first block in a blockchain or similar sequential ledger.
-
E.
initialAction
Indicates the first or starting action taken in a sequence of actions or events.
- 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_69f01a5d7ec88190ada2d5be7c06c35d |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a28b8ea881908733485374771c51 |
completed | May 3, 2026, 1:19 a.m. |
Created at: April 28, 2026, 3:30 a.m.