Triple
T24722098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oceanus Procellarum |
E612333
|
entity |
| Predicate | wasLandingRegionFor |
P124725
|
FINISHED |
| Object | Chang'e 5 |
—
|
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: Chang'e 5 | Statement: [Oceanus Procellarum, wasLandingRegionFor, Chang'e 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasLandingRegionFor Context triple: [Oceanus Procellarum, wasLandingRegionFor, Chang'e 5]
-
A.
intendedLandingRegion
Indicates the geographic area or region where something is planned or expected to land.
-
B.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
C.
wasLandingSiteDuring
Indicates that a location served as the landing site for a particular event, mission, or vehicle during a specified time or context.
-
D.
landedNear
Indicates that one entity has come to rest on a surface or location in close proximity to another specified entity or reference point.
-
E.
isMajorLandingRegion
chosen
Indicates that a location serves as a primary or significant area where landings (such as aircraft, spacecraft, or vessels) commonly occur.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 3:41 a.m.