Triple
T27684700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long March 8 |
E697995
|
entity |
| Predicate | firstFlightOrbit |
P7200
|
FINISHED |
| Object | Sun-synchronous orbit |
—
|
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: Sun-synchronous orbit | Statement: [Long March 8, firstFlightOrbit, Sun-synchronous orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFlightOrbit Context triple: [Long March 8, firstFlightOrbit, Sun-synchronous orbit]
-
A.
firstUseInOrbit
Indicates that this is the first time the object or system is being used while in orbit.
-
B.
firstOrbitalMission
Indicates that the subject entity carried out or was involved in the earliest orbital spaceflight mission associated with the object entity.
-
C.
orbitFirstReached
chosen
Indicates the point in time or event when an object first successfully enters into a specified orbit.
-
D.
firstOrbitalSuccessPayloadType
Indicates the type or category of payload carried on an entity’s first successful orbital mission.
-
E.
firstOrbitalMissionOutcome
Indicates the result or status achieved by an entity’s first orbital mission.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff49016dcc8190a8a43868c728b4f1 |
completed | May 9, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69ff4891924c8190b5be340e2520e012 |
completed | May 9, 2026, 2:45 p.m. |
Created at: April 27, 2026, 2:48 p.m.