Triple
T28543342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long March 7 |
E722359
|
entity |
| Predicate | successfullyLaunchedSpacecraft |
P7189
|
FINISHED |
| Object | Tianzhou-1 |
—
|
NE NERFINISHED |
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: Tianzhou-1 | Statement: [Long March 7, successfullyLaunchedSpacecraft, Tianzhou-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successfullyLaunchedSpacecraft Context triple: [Long March 7, successfullyLaunchedSpacecraft, Tianzhou-1]
-
A.
launchedSpacecraft
Indicates that one entity initiated the sending of a spacecraft into space.
-
B.
successfulLaunches
chosen
Indicates that one entity has carried out one or more launches that achieved their intended objectives without failure.
-
C.
launchSpacecraft
Indicates initiating the sending of a spacecraft from a launch site into space, typically by activating and controlling its launch vehicle.
-
D.
spacecraftLaunchAssociatedWith
Indicates a relationship where a spacecraft launch is connected or linked to another event, object, or entity involved in or affected by that launch.
-
E.
spaceStationLaunched
Indicates that a space station has been sent from Earth into space on a launch vehicle.
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 28, 2026, 3:37 a.m.