Triple
T32290775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yap Time |
E824959
|
entity |
| Predicate | standardTimeZoneOf |
P132463
|
FINISHED |
| Object | Yap State |
—
|
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: Yap State | Statement: [Yap Time, standardTimeZoneOf, Yap State]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTimeZoneOf Context triple: [Yap Time, standardTimeZoneOf, Yap State]
-
A.
javaTimeZoneID
Indicates that an entity is associated with a specific Java time zone identifier (e.g., "America/New_York") used for date and time operations.
-
B.
hasStandardTimeZone
chosen
Indicates that an entity is associated with a particular standard time zone used to define its official local time.
-
C.
timeZoneName
Indicates the specific time zone designation (such as its standard name or label) associated with an entity.
-
D.
timeZoneState
Indicates that one entity is a state or region associated with the time zone of another entity.
-
E.
timeZoneType
Indicates the classification or category of a time zone associated with an entity (e.g., standard, daylight, or specific time zone format/type).
- 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_69f349101b788190b4f14884dc7d1ed2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 12:44 a.m.