Triple
T2169331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandrayaan-3 |
E46985
|
entity |
| Predicate | landingSiteRegion |
P19379
|
FINISHED |
| Object | lunar south polar 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 south polar region | Statement: [Chandrayaan-3, landingSiteRegion, lunar south polar region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingSiteRegion Context triple: [Chandrayaan-3, landingSiteRegion, lunar south polar region]
-
A.
landingRegion
chosen
Indicates the area or zone where an object or entity comes to rest or makes contact after moving or descending.
-
B.
serviceRegion
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
C.
marketRegion
Indicates the geographic or demographic area in which a product, service, or entity is actively marketed or targeted.
-
D.
countryOrRegionUsed
Indicates that something is used within, or applies to, a specific country or geographic region.
-
E.
endpointRegion
Indicates that one entity serves as the geographic or logical region in which the other entity’s endpoint is located or configured.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.