Triple
T38395615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shepherd Gate Clock |
E900752
|
entity |
| Predicate | timeStandardDisplayed |
P6292
|
FINISHED |
| Object | GMT |
—
|
NE NERFINISHED |
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: GMT | Statement: [Shepherd Gate Clock, timeStandardDisplayed, GMT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeStandardDisplayed Context triple: [Shepherd Gate Clock, timeStandardDisplayed, GMT]
-
A.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
B.
timingStandard
Indicates that one entity specifies or conforms to the timing rules, constraints, or reference schedule defined by another entity.
-
C.
standardTimeName
chosen
Indicates the official name assigned to a particular standard time used in a region or context.
-
D.
standardTimeDesignation
Indicates that one entity designates or specifies the standard (non-daylight-saving) time applicable to another entity.
-
E.
isStandardTime
Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
- 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_69f76e6071a081909eea7a670d21420c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:31 p.m.