Triple
T2572952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NST |
E57704
|
entity |
| Predicate | relativeToAST |
P9276
|
FINISHED |
| Object | 30 minutes ahead of Atlantic Standard Time |
—
|
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: 30 minutes ahead of Atlantic Standard Time | Statement: [NST, relativeToAST, 30 minutes ahead of Atlantic Standard Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeToAST Context triple: [NST, relativeToAST, 30 minutes ahead of Atlantic Standard Time]
-
A.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
B.
reducesTo
Indicates that one expression, structure, or state can be transformed or simplified into another, typically more basic or canonical, form.
-
C.
movesRelativeTo
Indicates that one entity changes its position or orientation with respect to another entity, rather than with respect to a fixed reference frame.
-
D.
relationToUTC
chosen
Indicates the temporal offset or correspondence between a given time value and Coordinated Universal Time (UTC).
-
E.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3853c848190970e8a2da16d726d |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.