Triple
T11078571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubble (lunar crater) |
E261928
|
entity |
| Predicate | hasLocationRegion |
P64798
|
FINISHED |
| Object | far side highlands |
—
|
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: far side highlands | Statement: [Hubble (lunar crater), hasLocationRegion, far side highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationRegion Context triple: [Hubble (lunar crater), hasLocationRegion, far side highlands]
-
A.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
currentLocationRegion
Indicates the region in which an entity is presently located.
-
C.
placeRegion
chosen
Indicates that a place is located within, or is part of, a larger geographic or administrative region.
-
D.
locationRegion2
Indicates that an entity is located within, or associated with, a second or alternative geographic or administrative region.
-
E.
latitudeRegion
Indicates that an entity is located within, or associated with, a specific geographic region defined by latitude coordinates.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799953d58819096b645a1377e70f2 |
completed | April 9, 2026, 12:20 p.m. |
| PD | Predicate disambiguation | batch_69d74415403c81909778bcd829e8832e |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.