Triple
T4124319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lennep |
E92687
|
entity |
| Predicate | historicalRight |
P15548
|
FINISHED |
| Object | town charter |
—
|
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: town charter | Statement: [Lennep, historicalRight, town charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalRight Context triple: [Lennep, historicalRight, town charter]
-
A.
historicalRightGranted
chosen
Indicates that a right or privilege was formally granted to an entity at some point in the past.
-
B.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
C.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
D.
historicalLaw
Indicates that the referenced law or legal provision existed and was in effect during a past historical period, rather than being current.
-
E.
historicalForm
Indicates that one entity is an earlier or historically attested form or variant of another 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:41 p.m.