Triple

T32573104
Position Surface form Disambiguated ID Type / Status
Subject Shenzhou 13 E832567 entity
Predicate spaceStationModuleDockedTo P52854 FINISHED
Object Tianhe core module 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: Tianhe core module | Statement: [Shenzhou 13, spaceStationModuleDockedTo, Tianhe core module]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: spaceStationModuleDockedTo
Context triple: [Shenzhou 13, spaceStationModuleDockedTo, Tianhe core module]
  • A. spaceStationAssociation
    Indicates an affiliation or operational relationship between an entity and a specific space station, such as ownership, management, use, or service connection.
  • B. spaceStationModuleOf
    Indicates that one entity is a module or component that forms part of a particular space station.
  • C. spaceStationName
    Indicates that an entity has the specified name of a space station.
  • D. dockingWithISS
    Indicates a relationship where a spacecraft is physically connecting and securing itself to the International Space Station to enable transfer of crew, cargo, or resources.
  • E. spaceStationServed chosen
    Indicates that a particular space station is or was serviced, supplied, or supported by a specific mission, vehicle, or service entity.
  • 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_69f34927bb308190ad94da1b11cad13c completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f73223675481908c1bc3208c0f5284 completed May 3, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69f7317690108190b3aae2cd2e1d069e completed May 3, 2026, 11:28 a.m.
Created at: May 1, 2026, 1:04 a.m.