Triple
T333049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Stock Exchange |
E6664
|
entity |
| Predicate | continuousTradingStartLocal |
P2917
|
FINISHED |
| Object | 08: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: 08:00 | Statement: [London Stock Exchange, continuousTradingStartLocal, 08:00]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousTradingStartLocal Context triple: [London Stock Exchange, continuousTradingStartLocal, 08:00]
-
A.
hasTradingHours
chosen
Indicates that an entity operates or is available for trading during specified time periods.
-
B.
tradingStatus
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
-
C.
tradedSince
Indicates that an entity has been actively traded starting from a specified point in time and continuing thereafter.
-
D.
hasTradingDays
Indicates that an entity is associated with specific days on which trading or commercial transactions are conducted.
-
E.
tradedOn
Indicates that an asset, security, or instrument is bought and sold on a particular exchange or trading venue.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eac4d9d081908a624464e450fb0e |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94d99cc8190a112e4b630ec63c1 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.