Triple
T3492834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space-Based Infrared System |
E73776
|
entity |
| Predicate | firstGEOlaunchDate |
P48716
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Space-Based Infrared System, firstGEOlaunchDate, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGEOlaunchDate Context triple: [Space-Based Infrared System, firstGEOlaunchDate, 2011]
-
A.
firstOrbitalLaunchAttemptDate
Indicates the calendar date on which an entity made its first attempt to launch a vehicle into orbit.
-
B.
firstSatelliteLaunchDate
Indicates the calendar date on which an entity’s first satellite was launched into space.
-
C.
firstSuccessfulOrbitalLaunch
Indicates that the event is the earliest instance in which a launch successfully placed a payload into a stable orbit around a celestial body.
-
D.
launchDateOfFirstHumanSpaceflight
Indicates the calendar date on which the first human spaceflight associated with the given entity was launched.
-
E.
firstSpaceflight
Indicates that the subject entity performed, experienced, or was responsible for its earliest occurrence of traveling into outer space.
- 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_69ad85cca8d4819088494e9f3340fab5 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbabd1708190b1ca4cbc87462b5b |
completed | March 8, 2026, 6:10 p.m. |
| PD | Predicate disambiguation | batch_69adae0b34908190b2bb5766a2231f7a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb055ed2481908171effe28151cf9 |
completed | March 8, 2026, 5:22 p.m. |
Created at: March 8, 2026, 3:18 p.m.