Triple
T7553023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUI |
E178582
|
entity |
| Predicate | hasTradingHoursTimeZone |
P72277
|
FINISHED |
| Object | Eastern 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: Eastern Time | Statement: [RUI, hasTradingHoursTimeZone, Eastern Time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTradingHoursTimeZone Context triple: [RUI, hasTradingHoursTimeZone, Eastern Time]
-
A.
tradingHoursTimezone
chosen
Indicates the time zone in which an entity’s trading hours are defined and observed.
-
B.
hasTradingHours
Indicates that an entity operates or is available for trading during specified time periods.
-
C.
tradingHoursType
Indicates the classification of an entity’s trading hours, such as whether they are regular, extended, holiday-specific, or of another defined type.
-
D.
hasTimeZones
Indicates that an entity is associated with one or more time zones in which it is valid or operates.
-
E.
hasTradingSession
Indicates that an entity participates in or is associated with a specific trading session or period during which trading activities occur.
- 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b8165481908285fc9697fe4c99 |
completed | March 27, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.