Triple
T1480402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bakewell |
E30940
|
entity |
| Predicate | marketCharterStatus |
P19353
|
FINISHED |
| Object | historic |
—
|
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: historic | Statement: [Bakewell, marketCharterStatus, historic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketCharterStatus Context triple: [Bakewell, marketCharterStatus, historic]
-
A.
hasMarketCharterStatus
chosen
Indicates that an entity holds a specific official market charter status, such as being authorized, licensed, or otherwise formally recognized to operate in a designated market.
-
B.
hasMarketCharter
Indicates that an entity possesses an official authorization or charter granting it the right to operate as a market.
-
C.
hasMarketCharterSince
Indicates that an entity has held an official market charter continuously from a specified point in time onward.
-
D.
regulatedMarketFor
Indicates that one entity functions as a regulated market or trading venue specifically for the financial instruments, assets, or products associated with another entity.
-
E.
tradingStatus
Indicates the current state or condition of an entity’s ability to be traded or engaged in trading activities.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c674cc9c819088fc9146c7a7a914 |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.