Triple
T28599836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiangong-2 |
E723877
|
entity |
| Predicate | cargoMissionPurpose |
P53987
|
FINISHED |
| Object | test automated cargo resupply |
—
|
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: test automated cargo resupply | Statement: [Tiangong-2, cargoMissionPurpose, test automated cargo resupply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoMissionPurpose Context triple: [Tiangong-2, cargoMissionPurpose, test automated cargo resupply]
-
A.
cargoMission
Indicates a mission whose primary purpose is to transport cargo from one location to another.
-
B.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
C.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
-
D.
missionRationale
chosen
Indicates the underlying purpose, justification, or intended reason for undertaking a particular mission or operation.
-
E.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:23 a.m.