Triple
T14691858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Billingsgate Market |
E345053
|
entity |
| Predicate | grantedLegalStatusAsMarket |
P32451
|
FINISHED |
| Object | 1699 |
—
|
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: 1699 | Statement: [Billingsgate Market, grantedLegalStatusAsMarket, 1699]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedLegalStatusAsMarket Context triple: [Billingsgate Market, grantedLegalStatusAsMarket, 1699]
-
A.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
hasHighestLegalStatusWithinCountry
Indicates that an entity holds the topmost legally recognized status or rank within a specific country, above all other comparable statuses.
-
C.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
-
D.
grantedStatus
chosen
Indicates that an entity has been officially approved or given a particular status, permission, or privilege.
-
E.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb585d46c81908d6964130914cec4 |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.