Triple
T27674488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese astronaut corps |
E697742
|
entity |
| Predicate | usesDestination |
P165712
|
FINISHED |
| Object | Tiangong space station |
—
|
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: Tiangong space station | Statement: [Chinese astronaut corps, usesDestination, Tiangong space station]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDestination Context triple: [Chinese astronaut corps, usesDestination, Tiangong space station]
-
A.
isDestinationBased
Indicates that something is determined, organized, or classified according to its destination.
-
B.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
-
C.
hasDestinationRegion
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
D.
sampleDestination
Indicates that something serves as, or is designated to be, the target location or endpoint for a sample.
-
E.
servedDestination
Indicates that a service or action is directed toward, or provided to, a particular destination.
- 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_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 27, 2026, 2:43 p.m.