Triple
T32508232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 3 |
E830857
|
entity |
| Predicate | roverPrimaryObjective |
P175485
|
FINISHED |
| Object | in-situ exploration of lunar surface |
—
|
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: in-situ exploration of lunar surface | Statement: [Chang’e 3, roverPrimaryObjective, in-situ exploration of lunar surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roverPrimaryObjective Context triple: [Chang’e 3, roverPrimaryObjective, in-situ exploration of lunar surface]
-
A.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
B.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
C.
tertiaryMission
Indicates a relationship where an entity has a third-level or lower-priority mission or objective in addition to its primary and secondary missions.
-
D.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
E.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1 a.m.