Triple
T10430373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mise of Amiens |
E245895
|
entity |
| Predicate | legalEffectOnBarons |
P93545
|
FINISHED |
| Object | baronial concessions revoked |
—
|
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: baronial concessions revoked | Statement: [Mise of Amiens, legalEffectOnBarons, baronial concessions revoked]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalEffectOnBarons Context triple: [Mise of Amiens, legalEffectOnBarons, baronial concessions revoked]
-
A.
hasNotableBarony
Indicates that an entity possesses or is associated with a barony that is considered notable or significant in some context.
-
B.
createdBaronOrBaronessOf
Indicates that one entity granted or established the noble title of baron or baroness for another entity.
-
C.
historicBarony
Indicates that an entity has the status or role of a historic barony, i.e., it was once recognized as a baronial territorial or feudal jurisdiction.
-
D.
lordOf
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
E.
hasFeudalOverlord
Indicates that one entity holds feudal lordship or overlord authority over another, implying hierarchical control and obligations within a feudal system.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea62d6448190a7f5b785467824cf |
completed | April 7, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_69d4dfbc546881908f312c66ee195f79 |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91de3088190ae89cbb12fb29db8 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:13 p.m.