Triple
T30984181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSE: HOF |
E789473
|
entity |
| Predicate | hadPrimaryListing |
P15706
|
FINISHED |
| Object | House of Fraser |
—
|
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: House of Fraser | Statement: [LSE: HOF, hadPrimaryListing, House of Fraser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPrimaryListing Context triple: [LSE: HOF, hadPrimaryListing, House of Fraser]
-
A.
primaryListing
chosen
Indicates that one item in a set of listings is designated as the main or most authoritative listing for a given entity or context.
-
B.
secondaryListing
Indicates that an item, asset, or entity is listed or offered in an additional, non-primary venue or context beyond its main listing.
-
C.
primaryListingMarket
Indicates the market or exchange where a security is first and principally listed for trading.
-
D.
hasHistoricListing
Indicates that an entity is officially recorded or recognized as having historic or heritage significance, typically through inclusion in a formal historic register or listing.
-
E.
listedThrough
Indicates that an item, service, or asset is made available or advertised via a particular platform, intermediary, or listing channel.
- 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_69f224c550b081909ddfceb0c3d03bdd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:55 p.m.