Triple
T2097259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henley-on-Thames |
E37009
|
entity |
| Predicate | grantedMarketCharter |
P20115
|
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: [Henley-on-Thames, grantedMarketCharter, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grantedMarketCharter Context triple: [Henley-on-Thames, grantedMarketCharter, 13th century]
-
A.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
B.
hasCharter
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
-
C.
hasMarketCharter
chosen
Indicates that an entity possesses an official authorization or charter granting it the right to operate as a market.
-
D.
grantedIn
Indicates that something (such as a right, status, or permission) is formally conferred or authorized within a particular context, document, or jurisdiction.
-
E.
charterConfirmedBy
Indicates that an official charter has been formally approved or validated by a specified authority or entity.
- 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_69a8861828948190924aa30c08806b3a |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba9cb84481909fe0a66c020b8864 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.