Triple
T7922843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xichang Satellite Launch Center |
E183986
|
entity |
| Predicate | hasLaunchPads |
P39161
|
FINISHED |
| Object | multiple launch complexes |
—
|
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 launch complexes | Statement: [Xichang Satellite Launch Center, hasLaunchPads, multiple launch complexes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchPads Context triple: [Xichang Satellite Launch Center, hasLaunchPads, multiple launch complexes]
-
A.
hasLaunchPadNumber
Indicates that an entity (such as a launch site or facility) is associated with a specific launch pad identification number.
-
B.
launchPadsCount
chosen
Indicates the number of launch pads associated with or available at a given entity or location.
-
C.
hasSpaceport
Indicates that a location or entity possesses or hosts a spaceport facility for spacecraft operations.
-
D.
hasShuttlecraft
Indicates that an entity possesses, controls, or is equipped with one or more shuttlecraft.
-
E.
hasShuttleBay
Indicates that an entity possesses or is equipped with a shuttle bay as part of its structure or facilities.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aaadd1c8190971f2a6c7636cae4 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:06 p.m.