Triple
T128850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York Stock Exchange |
E2606
|
entity |
| Predicate | standardTradingHoursLocalTime |
P2917
|
FINISHED |
| Object | 09:30–16:00 |
—
|
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: 09:30–16:00 | Statement: [New York Stock Exchange, standardTradingHoursLocalTime, 09:30–16:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTradingHoursLocalTime Context triple: [New York Stock Exchange, standardTradingHoursLocalTime, 09:30–16:00]
-
A.
hasTradingHours
chosen
Indicates that an entity operates or is available for trading during specified time periods.
-
B.
hasPreMarketSession
Indicates that a financial instrument or market has a designated trading session that occurs before the regular market hours.
-
C.
isOneHourAheadOf
Indicates that one entity’s local time is exactly one hour later than the other entity’s local time.
-
D.
capitalTimeZoneOf
Indicates that a specified time zone is the primary or official time zone in which a given capital city is located or operates.
-
E.
hasTradingDays
Indicates that an entity is associated with specific days on which trading or commercial transactions are conducted.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a2576518e0819096b35d8af7a4d1bd |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564da96c8190aa8204de25229c15 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.