Triple
T18919322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Mortain |
E462803
|
entity |
| Predicate | declineAsAutonomousLordshipCentury |
P133800
|
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: [County of Mortain, declineAsAutonomousLordshipCentury, 13th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declineAsAutonomousLordshipCentury Context triple: [County of Mortain, declineAsAutonomousLordshipCentury, 13th century]
-
A.
declineBeganInCentury
Indicates that the period of decline for an entity started during a specified century.
-
B.
vassalageEndedBy
Indicates that a prior vassal relationship between two entities has been terminated by a specific third party or event.
-
C.
vassalageEndTime
Indicates the point in time at which a vassalage relationship between two entities formally ends.
-
D.
declinedAfterCentury
Indicates that something experienced a reduction, deterioration, or loss of prominence after the end of a specified century.
-
E.
ruledUntilCentury
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) a specified century.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c629527481909dad169f07df0da4 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
| PDg | Predicate description generation | batch_69e4ad8e075c8190ad561edc5e520057 |
completed | April 19, 2026, 10:25 a.m. |
Created at: April 10, 2026, 11:59 a.m.