Triple
T4127180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLIM |
E92752
|
entity |
| Predicate | landingSiteType |
P15047
|
FINISHED |
| Object | lunar near-side region |
—
|
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 near-side region | Statement: [SLIM, landingSiteType, lunar near-side region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingSiteType Context triple: [SLIM, landingSiteType, lunar near-side region]
-
A.
typeOfSite
chosen
Indicates the specific category or kind of site that an entity is classified as.
-
B.
siteTypeServed
Indicates the type of site or location that is served, supported, or handled by a given entity or resource.
-
C.
landingSiteAttempt
Indicates an attempt by an entity to use or reach a particular location as a landing site, regardless of whether the landing ultimately succeeds.
-
D.
landing
Indicates the action or event of an entity coming down from the air or a higher position to make controlled contact with a surface.
-
E.
landingArea
Indicates that a location or surface serves as a designated area where something (such as an aircraft, object, or person) can land.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:42 p.m.