Triple

T9232331
Position Surface form Disambiguated ID Type / Status
Subject LightSail 2 E221846 entity
Predicate deploymentEvent P16817 FINISHED
Object solar sail deployed in orbit on 2019-07-23 — 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: solar sail deployed in orbit on 2019-07-23 | Statement: [LightSail 2, deploymentEvent, solar sail deployed in orbit on 2019-07-23]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: deploymentEvent
Context triple: [LightSail 2, deploymentEvent, solar sail deployed in orbit on 2019-07-23]
  • A. deploys chosen
    Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
  • B. deploymentTime
    Indicates the point in time at which something is deployed, initiated, or put into operation.
  • C. launchEvent
    Indicates an event in which something is formally initiated, introduced, or set into operation.
  • D. formationEvent
    Indicates the event or process through which something comes into existence, is created, or is initially established.
  • E. deploymentRequires
    Indicates that performing a particular deployment is contingent upon the prior existence, completion, or availability of another specified resource, condition, or action.
  • 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_69ca83ed628c8190bc02d641e57f097f completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccee1a7e9881908e0c11f242162017 completed April 1, 2026, 10:06 a.m.
PD Predicate disambiguation batch_69cc7a3daeb481908b0abde3fbc1f1f0 completed April 1, 2026, 1:51 a.m.
Created at: March 30, 2026, 7:29 p.m.