Triple
T29761355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airy (lunar crater) |
E753778
|
entity |
| Predicate | isOnNearSide |
P47353
|
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: [Airy (lunar crater), isOnNearSide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnNearSide Context triple: [Airy (lunar crater), isOnNearSide, true]
-
A.
nearSideOrFarSide
Indicates that one entity is located on either the near side or the far side of another reference point or object, distinguishing relative positional sides.
-
B.
locatedOnSideOfMoon
chosen
Indicates that one entity is situated on a specific side or hemisphere of the Moon relative to another reference frame or viewpoint.
-
C.
isOuterMoonRelativeTo
Indicates that one celestial body orbits farther from the central object than another, making it the more distant (outer) moon in their relative configuration.
-
D.
isNearCelestialEquator
Indicates that one celestial object or position lies close to the celestial equator in the sky.
-
E.
isOnMoon
Indicates that one entity is physically located on the surface of the Moon.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f673d041448190a414a19cf28b09d2 |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 8:33 p.m.