Triple
T19314964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJTM |
E483071
|
entity |
| Predicate | hasLocationLongitude |
P1282
|
FINISHED |
| Object | approximately 139.4106° E |
—
|
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: approximately 139.4106° E | Statement: [RJTM, hasLocationLongitude, approximately 139.4106° E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationLongitude Context triple: [RJTM, hasLocationLongitude, approximately 139.4106° E]
-
A.
coordinateLongitude
chosen
Indicates the east–west geographic position of an entity on the Earth’s surface, expressed as a longitude value.
-
B.
landingSiteLongitude
Indicates the longitudinal coordinate (east–west position) of a specified landing site on a planetary body.
-
C.
intendedLongitude
Indicates the longitude value that an entity is meant or planned to have or reach, rather than its actual current longitude.
-
D.
hostCityLongitude
Indicates the longitudinal coordinate of the city that serves as the host location for an event or entity.
-
E.
hasSummitLongitude
Indicates the longitudinal coordinate at which the summit or highest point of an entity is located.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d833034819092a8414d5e0fc26e |
completed | April 20, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.