Triple
T9838036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SPOT Earth observation satellites |
E239151
|
entity |
| Predicate | launchOfFirstUnit |
P7203
|
FINISHED |
| Object | 1986-02-22 |
—
|
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: 1986-02-22 | Statement: [SPOT Earth observation satellites, launchOfFirstUnit, 1986-02-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchOfFirstUnit Context triple: [SPOT Earth observation satellites, launchOfFirstUnit, 1986-02-22]
-
A.
firstSuccessfulLaunchDate
chosen
Indicates the calendar date on which an entity achieved its first successful launch.
-
B.
firstDeployedIn
Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
-
C.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
D.
firstDeployedAt
Indicates the date and time when an entity was initially put into use or made operational.
-
E.
firstProductAnnounced
Indicates that an entity is the earliest (chronologically first) product publicly announced by another entity.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb347ff4c81908c312548a25bae71 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.