Triple
T32796333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang’e 8 |
E838773
|
entity |
| Predicate | willSupport |
P16415
|
FINISHED |
| Object | future crewed lunar missions |
—
|
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: future crewed lunar missions | Statement: [Chang’e 8, willSupport, future crewed lunar missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: willSupport Context triple: [Chang’e 8, willSupport, future crewed lunar missions]
-
A.
wouldProvide
Indicates that one entity is willing or expected to supply or furnish something to another entity under certain conditions.
-
B.
willProvision
Indicates that one entity is obligated or scheduled to provide, supply, or allocate resources or services to another entity in the future.
-
C.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
D.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
E.
providesSupportTo
chosen
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
- 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_69f3493c7f6881908edf2aa13631d1e0 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.