Triple
T15637425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTC−11 time zone |
E375981
|
entity |
| Predicate | standardTimeUsedFor |
P6292
|
FINISHED |
| Object | civil time in American Samoa |
—
|
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: civil time in American Samoa | Statement: [UTC−11 time zone, standardTimeUsedFor, civil time in American Samoa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTimeUsedFor Context triple: [UTC−11 time zone, standardTimeUsedFor, civil time in American Samoa]
-
A.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
B.
standardTimeName
chosen
Indicates the official name assigned to a particular standard time used in a region or context.
-
C.
standardTimeCounterpart
Indicates that one time representation is the corresponding value expressed in a standard or canonical time format for the other.
-
D.
isStandardTime
Indicates that a given time value is expressed in standard (non-daylight-saving) time for its associated time zone.
-
E.
isStandardTimeFor
Indicates that a specified time zone or region is currently observing its standard (non-daylight-saving) time.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eba51f08190ac5d9de7fc89405a |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.