Triple
T9288904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AIM |
E223465
|
entity |
| Predicate | listingVenue |
P41818
|
FINISHED |
| Object | London Stock Exchange electronic order book |
—
|
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: London Stock Exchange electronic order book | Statement: [AIM, listingVenue, London Stock Exchange electronic order book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listingVenue Context triple: [AIM, listingVenue, London Stock Exchange electronic order book]
-
A.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
B.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
C.
usesVenues
Indicates that one entity makes use of or operates within specific venues or locations to carry out its activities or services.
-
D.
homeVenueAlsoUsedBy
Indicates that the venue serving as a home location for one entity is also used as a venue by another entity.
-
E.
hasListingVenue
chosen
Indicates that an item, event, or offering is associated with the specific venue where it is listed or made available.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0862b34c819097cb7c1777313925 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.