Triple
T32011167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilkeston |
E817404
|
entity |
| Predicate | charterFairFirstHeld |
P180819
|
FINISHED |
| Object | 13th century |
—
|
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: 13th century | Statement: [Ilkeston, charterFairFirstHeld, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterFairFirstHeld Context triple: [Ilkeston, charterFairFirstHeld, 13th century]
-
A.
charterDate
Indicates the date on which an organization, institution, or entity was formally established or granted its charter.
-
B.
charterFairMonth
Indicates the month during which a fair is officially authorized or chartered to take place.
-
C.
firstEditionHeldIn
Indicates the location where the first edition or initial occurrence of an event was held.
-
D.
charterAdoptedIn
Indicates that a charter was formally adopted or enacted at a specific time or in a specific place.
-
E.
charterEnteredIntoForce
Indicates that a charter has become legally effective and binding as of a specific point in time.
- F. None of above. chosen
Provenance (4 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
| PDg | Predicate description generation | batch_69f7516c538481908c6e55cf76add098 |
completed | May 3, 2026, 1:45 p.m. |
Created at: May 1, 2026, 12:15 a.m.