Triple
T27674412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianhe |
E697740
|
entity |
| Predicate | docksWith |
P54674
|
FINISHED |
| Object | Tianzhou cargo spacecraft |
—
|
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: Tianzhou cargo spacecraft | Statement: [Tianhe, docksWith, Tianzhou cargo spacecraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: docksWith Context triple: [Tianhe, docksWith, Tianzhou cargo spacecraft]
-
A.
docking
chosen
Indicates the action of one vehicle or structure aligning and securely connecting to another for transfer, access, or support.
-
B.
dockIncludes
Indicates that a dock contains, encompasses, or has as part of its structure the specified element or component.
-
C.
berthingOrDockingTarget
Indicates that an entity serves as the location or structure where a vessel or vehicle is intended to berth or dock.
-
D.
hasWharf
Indicates that one place or facility possesses or is equipped with a wharf for docking boats or ships.
-
E.
mooredAt
Indicates that one object, typically a vessel or floating structure, is secured or anchored at a specific location or facility.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 2:43 p.m.