Triple
T31082484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schippenbeil |
E792137
|
entity |
| Predicate | wasTownCharterHolder |
P8747
|
FINISHED |
| Object | medieval town law (historically) |
—
|
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: medieval town law (historically) | Statement: [Schippenbeil, wasTownCharterHolder, medieval town law (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasTownCharterHolder Context triple: [Schippenbeil, wasTownCharterHolder, medieval town law (historically)]
-
A.
hadBoroughCharter
Indicates that an entity was formally granted a borough charter, conferring it the legal status and privileges of a borough.
-
B.
hasCharter
chosen
Indicates that an entity possesses, is governed by, or operates under a formal charter or foundational document.
-
C.
hasCharterStatus
Indicates that an entity possesses a specific charter designation or status granted by an authoritative body.
-
D.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
E.
isFirstCharteredTownOf
Indicates that one town holds the status of being the earliest or first officially chartered town relative to another specified context or region.
- 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_69f224ce48348190bd0fc23f656ed683 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695fab50c81908c79fb84d3a94df9 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.