Triple
T32935217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culmerland |
E842507
|
entity |
| Predicate | hasMedievalCharterTradition |
P197859
|
FINISHED |
| Object | Chełmno law |
—
|
NE NERFINISHED |
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: Chełmno law | Statement: [Culmerland, hasMedievalCharterTradition, Chełmno law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMedievalCharterTradition Context triple: [Culmerland, hasMedievalCharterTradition, Chełmno law]
-
A.
medievalStatus
Indicates the social, legal, or hierarchical standing an entity holds within a medieval societal structure.
-
B.
chivalricTradition
Indicates a relationship where behaviors, values, or actions conform to or are guided by the codes and ideals of chivalry.
-
C.
hasMedievalElements
Indicates that something incorporates characteristics, motifs, or features typical of the medieval period.
-
D.
medievalState
Indicates that an entity functioned as a state or political unit during the medieval historical period.
-
E.
medievalAssociation
Indicates a relationship or involvement between entities specifically within a medieval context, such as shared roles, activities, or affiliations characteristic of the Middle Ages.
- 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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feb342994081909481ec8ec5d44928 |
completed | May 9, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69feb046e4e48190b96649aa28529cc9 |
completed | May 9, 2026, 3:55 a.m. |
| PDg | Predicate description generation | batch_69feb3419158819082f4666077535ca9 |
completed | May 9, 2026, 4:08 a.m. |
Created at: May 1, 2026, 1:20 a.m.