Triple
T29468476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagarin (walled plain) |
E747445
|
entity |
| Predicate | hasLocationRelativeToEarth |
P81574
|
FINISHED |
| Object | far side |
—
|
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 | Statement: [Gagarin (walled plain), hasLocationRelativeToEarth, far side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationRelativeToEarth Context triple: [Gagarin (walled plain), hasLocationRelativeToEarth, far side]
-
A.
positionRelativeToEarth
chosen
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
B.
motionRelativeToEarth
Indicates movement or change in position of an entity as measured or perceived relative to the Earth as a reference frame.
-
C.
hasApproximateDistanceFromEquator
Indicates that one entity has an approximate measured or estimated distance from the Earth's equator.
-
D.
firstKnownLocationOnEarth
Indicates the earliest known place on Earth where the entity was present, discovered, or recorded.
-
E.
hasSatelliteLocation
Indicates that an entity has a secondary or remote location associated with it, such as a branch, satellite office, or auxiliary site.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 28, 2026, 3:55 p.m.