Triple
T19348589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 8 |
E483949
|
entity |
| Predicate | landingLatitude |
P1281
|
FINISHED |
| Object | about -10 degrees |
—
|
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: about -10 degrees | Statement: [Venera 8, landingLatitude, about -10 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingLatitude Context triple: [Venera 8, landingLatitude, about -10 degrees]
-
A.
landingSiteLongitude
Indicates the longitudinal coordinate (east–west position) of a specified landing site on a planetary body.
-
B.
coordinateLatitude
chosen
Indicates the north–south geographic position of an entity on the Earth’s surface, expressed as a latitude coordinate.
-
C.
landingPlace
Indicates the location or surface where something or someone comes down to rest after moving through the air or space.
-
D.
hostCityLatitude
Indicates the geographic latitude coordinate of the city that serves as the host location for an event or entity.
-
E.
lowestLatitude
Indicates that one entity has a latitude value that is lower (i.e., farther south) than another entity or than all others in a given set.
- 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185d54c0819081715ca13a5806b4 |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
Created at: April 10, 2026, 1:34 p.m.