Triple
T27684707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long March 8 |
E697995
|
entity |
| Predicate | successRecord |
P189331
|
FINISHED |
| Object | multiple successful launches |
—
|
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: multiple successful launches | Statement: [Long March 8, successRecord, multiple successful launches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successRecord Context triple: [Long March 8, successRecord, multiple successful launches]
-
A.
successRate
Indicates the proportion or frequency with which attempts at a given action or process result in a successful outcome.
-
B.
successMetric
Indicates the specific criterion or measure used to evaluate whether an action, process, or relationship has achieved its intended success.
-
C.
finishedRecord
Indicates that an entity has completed or finalized the creation, processing, or updating of a record.
-
D.
successPeriod
Indicates the time span during which a particular action, process, or entity is considered successful or yields successful outcomes.
-
E.
succeededUnder
Indicates that one entity achieved success or attained a position while operating under the authority, leadership, or conditions established by another entity.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: April 27, 2026, 2:48 p.m.