Triple
T10451165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iridium satellite system |
E246425
|
entity |
| Predicate | initialDeploymentCompletionDate |
P88436
|
FINISHED |
| Object | 1998 |
—
|
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: 1998 | Statement: [Iridium satellite system, initialDeploymentCompletionDate, 1998]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialDeploymentCompletionDate Context triple: [Iridium satellite system, initialDeploymentCompletionDate, 1998]
-
A.
deploymentTime
Indicates the point in time at which something is deployed, initiated, or put into operation.
-
B.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
C.
commissioningEndDate
Indicates the date on which the commissioning process or commissioning-related responsibilities are completed or terminated.
-
D.
deploymentEnd
chosen
Indicates the point in time or event at which a deployment process or deployment state comes to an end.
-
E.
landerDeploymentDate
Indicates the date on which a lander is deployed or placed into its intended operational environment.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe0a6a548190a54212912f618e4e |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb73a5e48190a8df4775bc5da80f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.