Triple
T33279436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Universal Stores |
E851997
|
entity |
| Predicate | hasShareListing |
P78340
|
FINISHED |
| Object | London Stock Exchange |
—
|
NE NERFINISHED |
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 | Statement: [Great Universal Stores, hasShareListing, London Stock Exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShareListing Context triple: [Great Universal Stores, hasShareListing, London Stock Exchange]
-
A.
shareListing
Indicates that one entity distributes or makes a listing accessible to another entity or group.
-
B.
sharedListingWith
Indicates that one entity has made a listing (such as an item, property, or resource) available jointly or in common with another entity.
-
C.
hasListingAuthority
Indicates that an entity has the official power or permission to create, approve, or manage listings for another entity or resource.
-
D.
hasOwnerShare
Indicates that an entity holds a specified ownership stake or share in another entity or asset.
-
E.
isListed
chosen
Indicates that an entity appears on or is included in a specified list, registry, or catalog.
- 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_69f349653da08190819876015a298fdb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:32 a.m.