Triple
T22665867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WITA |
E559785
|
entity |
| Predicate | relativeToWIB |
P68497
|
FINISHED |
| Object | +1 hour |
—
|
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: +1 hour | Statement: [WITA, relativeToWIB, +1 hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToWIB Context triple: [WITA, relativeToWIB, +1 hour]
-
A.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
relativeToWesternIndonesiaTime
chosen
Indicates that the timing or temporal reference of an event or state is expressed in relation to Western Indonesia Time (WIB), serving as the baseline time zone for interpretation.
-
C.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
D.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
E.
relativeToHST
Indicates that something is defined, measured, or interpreted in relation to the Hubble Space Telescope (HST) as the reference frame or context.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781c2c808190baf6964ca1eced6f |
completed | April 29, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:08 p.m.