Triple
T2772039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indochina Time |
E61477
|
entity |
| Predicate | followsSolarTimeApproximatelyOf |
P11830
|
FINISHED |
| Object | 105th meridian east |
—
|
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: 105th meridian east | Statement: [Indochina Time, followsSolarTimeApproximatelyOf, 105th meridian east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsSolarTimeApproximatelyOf Context triple: [Indochina Time, followsSolarTimeApproximatelyOf, 105th meridian east]
-
A.
observesSameTimeAs
Indicates that two observation events occur simultaneously or during the same time interval.
-
B.
SunLocation
Indicates the spatial position or placement of the sun relative to a reference point or environment.
-
C.
forSunApprox
chosen
Indicates that something is approximately intended or suitable for use with, by, or in relation to the Sun, rather than being an exact or strictly defined solar relation.
-
D.
hasSolarDayLength
Indicates that an entity is associated with a specific duration for one complete solar day (the time between successive noons).
-
E.
followedByTimeZone
Indicates that one time zone chronologically succeeds another in a defined ordering or sequence.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.