Triple
T17769505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romford |
E443594
|
entity |
| Predicate | marketCharterGranted |
P16265
|
FINISHED |
| Object | 1247 |
—
|
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: 1247 | Statement: [Romford, marketCharterGranted, 1247]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketCharterGranted Context triple: [Romford, marketCharterGranted, 1247]
-
A.
hasMarketCharter
Indicates that an entity possesses an official authorization or charter granting it the right to operate as a market.
-
B.
hasMarketCharterStatus
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.
-
C.
hasMarketCharterSince
chosen
Indicates that an entity has held an official market charter continuously from a specified point in time onward.
-
D.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
E.
clubCharter
Indicates that there exists a formal charter or foundational document that defines the rules, purpose, and governance structure of a club.
- 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_69d8b9edf16c8190a59ebd245d378f4f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e485fe70648190b4107e1eabacc694 |
completed | April 19, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:11 a.m.