Triple
T32573019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 4 |
E832565
|
entity |
| Predicate | targetHemisphere |
P40962
|
FINISHED |
| Object | lunar far side |
—
|
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: lunar far side | Statement: [Chang’e 4, targetHemisphere, lunar far side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetHemisphere Context triple: [Chang’e 4, targetHemisphere, lunar far side]
-
A.
visibleInHemisphere
chosen
Indicates that an object or phenomenon can be seen or observed from a specified hemisphere of a celestial body.
-
B.
hemisphereLeading
Indicates that one hemisphere (e.g., of a brain or celestial body) is dominant, primary, or takes the leading role relative to the other.
-
C.
targetSide
Indicates the specific side or aspect of a referenced target that is involved in or affected by the relationship or action.
-
D.
hasPeakUsageInHemisphere
Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
-
E.
hemisphereSpecificity
Indicates that the relationship, property, or effect applies specifically to one cerebral hemisphere (left or right) rather than bilaterally.
- 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_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: May 1, 2026, 1:04 a.m.