Triple
T31732973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinner, Middlesex, England |
E809910
|
entity |
| Predicate | Pinner Fair firstHeld |
P131534
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [Pinner, Middlesex, England, Pinner Fair firstHeld, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Pinner Fair firstHeld Context triple: [Pinner, Middlesex, England, Pinner Fair firstHeld, 14th century]
-
A.
Pinner Fair
Indicates a fair or event taking place in, associated with, or named after Pinner.
-
B.
firstEditionHeldIn
Indicates the location where the first edition or initial occurrence of an event was held.
-
C.
firstHeldApproximate
chosen
Indicates that an entity’s initial holding or possession of something is known only approximately in time or value, rather than with exact precision.
-
D.
firstInPark
Indicates that one entity is the earliest or first to arrive, appear, or be present in a specified park relative to other entities.
-
E.
firstHeldAtVenue
Indicates that an event was initially held at a particular venue for the first time.
- 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:22 p.m.