Triple
T11651318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRVG |
E276909
|
entity |
| Predicate | tradesDuring |
P100189
|
FINISHED |
| Object | NASDAQ regular trading hours |
—
|
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: NASDAQ regular trading hours | Statement: [TRVG, tradesDuring, NASDAQ regular trading hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradesDuring Context triple: [TRVG, tradesDuring, NASDAQ regular trading hours]
-
A.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
B.
tradedSince
Indicates that an entity has been actively traded starting from a specified point in time and continuing thereafter.
-
C.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
D.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
E.
actualTrading
Indicates the occurrence of real, executed trading activity between parties, as opposed to planned, simulated, or potential trades.
- F. None of above. chosen
Provenance (4 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.