Triple
T32573016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 4 |
E832565
|
entity |
| Predicate | usesRelaySatellite |
P181178
|
FINISHED |
| Object | Queqiao |
—
|
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: Queqiao | Statement: [Chang’e 4, usesRelaySatellite, Queqiao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRelaySatellite Context triple: [Chang’e 4, usesRelaySatellite, Queqiao]
-
A.
supportsRelayAgents
Indicates that one entity is capable of working with or providing functionality for relay agents that forward or mediate communications between other entities.
-
B.
secondRelayOperatedBy
Indicates that a second relay device is controlled or actuated by a specified operator or system.
-
C.
isDistantSatelliteOf
Indicates that one celestial body orbits another at a relatively large distance, functioning as a far-removed satellite of that primary body.
-
D.
hasInterSatelliteLinks
Indicates that there exist communication or data-transfer links directly connecting one satellite to one or more other satellites.
-
E.
hasSatelliteTerminal
Indicates that an entity is equipped with or connected to a satellite communication terminal.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
| PDg | Predicate description generation | batch_69f762651e088190baa21f25378a6065 |
completed | May 3, 2026, 2:57 p.m. |
Created at: May 1, 2026, 1:04 a.m.