Triple
T27674100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base 25 |
E697734
|
entity |
| Predicate | hasLaunchPadsFor |
P186352
|
FINISHED |
| Object | Long March rockets |
—
|
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: Long March rockets | Statement: [Base 25, hasLaunchPadsFor, Long March rockets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchPadsFor Context triple: [Base 25, hasLaunchPadsFor, Long March rockets]
-
A.
hasLandingSystem
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
-
B.
hasLaunchPadNumber
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
-
C.
isPrimarySpaceportOf
Indicates that a given spaceport serves as the main or principal launch and operations facility for a specified region, organization, or celestial body.
-
D.
hasSpaceport
Indicates that a location or entity possesses or hosts a spaceport facility for spacecraft operations.
-
E.
usesLaunchVehiclesFrom
Indicates that one entity conducts its launches by employing launch vehicles that originate from or are provided 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 27, 2026, 2:42 p.m.