Triple
T10451164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iridium satellite system |
E246425
|
entity |
| Predicate | initialDeploymentStartDate |
P26529
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Iridium satellite system, initialDeploymentStartDate, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialDeploymentStartDate Context triple: [Iridium satellite system, initialDeploymentStartDate, 1997]
-
A.
firstDeployedAt
chosen
Indicates the date and time when an entity was initially put into use or made operational.
-
B.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
C.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
D.
estimatedInitialExpansionDate
Indicates the date on which the initial expansion of something (such as a project, system, or operation) is estimated to have begun or will begin.
-
E.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
- 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.