Triple
T28711022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVHRR |
E729830
|
entity |
| Predicate | firstLaunchOn |
P110715
|
FINISHED |
| Object | TIROS-N satellite |
—
|
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: TIROS-N satellite | Statement: [AVHRR, firstLaunchOn, TIROS-N satellite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstLaunchOn Context triple: [AVHRR, firstLaunchOn, TIROS-N satellite]
-
A.
firstModuleLaunch
Indicates the event or relationship where the initial module of a system, project, or mission is launched or activated for the first time.
-
B.
firstLaunchMission
chosen
Indicates that a mission is the first launch associated with a particular object, program, or entity.
-
C.
launchesOn
Indicates that one entity initiates or begins another entity (such as a process, event, or object) at a specific time or on a specific date.
-
D.
firstInstallation
Indicates that an entity represents the earliest or initial installation event or instance associated with another entity.
-
E.
firstProductLaunch
Indicates that an entity is carrying out or associated with its initial product introduction to the market.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_6a004fd3caf48190b2ec063a7bf0756b |
completed | May 10, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_6a004f7672dc8190aca91d1ed855bf9a |
completed | May 10, 2026, 9:27 a.m. |
Created at: April 28, 2026, 5:48 a.m.