Triple
T16920088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chryse Planitia |
E410422
|
entity |
| Predicate | isMajorLandingRegion |
P124725
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Chryse Planitia, isMajorLandingRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorLandingRegion Context triple: [Chryse Planitia, isMajorLandingRegion, true]
-
A.
isMajorRegionFor
Indicates that a region serves as a primary or significant area associated with a particular entity, activity, or phenomenon.
-
B.
isMajorRegionalCenter
Indicates that a location functions as a primary hub of economic, administrative, or cultural activity within a specific geographic region.
-
C.
hasMajorLocation
Indicates that an entity is primarily situated in, based in, or most significantly associated with a particular location.
-
D.
isMajorRegionalAirportFor
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
E.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cded2f8481909a20cc08b47e922e |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.