Triple
T31397694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 United States census |
E800903
|
entity |
| Predicate | timeZoneOfReferenceMoment |
P26707
|
FINISHED |
| Object | local time in each place |
—
|
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: local time in each place | Statement: [1980 United States census, timeZoneOfReferenceMoment, local time in each place]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeZoneOfReferenceMoment Context triple: [1980 United States census, timeZoneOfReferenceMoment, local time in each place]
-
A.
timeOffsetReference
Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
-
B.
timeZoneDependence
Indicates how a process, value, or behavior changes or is determined based on the time zone in which it is considered.
-
C.
timeZoneContext
chosen
Indicates the time zone setting or context in which an event, action, or relationship is interpreted.
-
D.
timeZoneOffsetOrigin
Indicates the time difference between an entity’s local time and a defined origin or reference time zone.
-
E.
timezoneBasis
Indicates that one timezone is defined, measured, or interpreted in reference to another timezone as its underlying standard or point of comparison.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 29, 2026, 9:19 p.m.