Triple
T865281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSK |
E18687
|
entity |
| Predicate | timeStandardType |
P4820
|
FINISHED |
| Object | 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: standard time | Statement: [MSK, timeStandardType, standard time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeStandardType Context triple: [MSK, timeStandardType, standard time]
-
A.
timeType
Indicates the specific temporal category or classification associated with a time-related entity or value (e.g., duration, point in time, interval, or recurrence type).
-
B.
standardTimeName
Indicates the official name assigned to a particular standard time used in a region or context.
-
C.
timeNotation
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
-
D.
timeZoneType
chosen
Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
-
E.
standardTimeCounterpart
Indicates that one time representation is the corresponding value expressed in a standard or canonical time format for the other.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac6acc148190bcc00a1e939ace77 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa86065881909d477e26fdd84d45 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.