Triple
T18919314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | County of Mortain |
E462803
|
entity |
| Predicate | laterSuzerainty |
P5603
|
FINISHED |
| Object | King of France |
—
|
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: King of France | Statement: [County of Mortain, laterSuzerainty, King of France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSuzerainty Context triple: [County of Mortain, laterSuzerainty, King of France]
-
A.
governedUnderSuzeraintyOf
Indicates that one entity exercises suzerain authority over another, which retains limited internal autonomy but is politically subordinate in key matters such as foreign policy or defense.
-
B.
suzerain
chosen
Indicates a relationship in which one entity holds overlordship or supreme authority over another, which remains internally autonomous but owes allegiance, tribute, or obedience.
-
C.
formerSovereign
Indicates that an entity once held sovereign (ruling) authority over another entity but no longer does.
-
D.
sovereignStateAfter
Indicates that one sovereign state succeeds another as its political or legal successor in time.
-
E.
laterMonarch
Indicates that one monarch’s reign occurred after another monarch’s reign in time.
- 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_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. |
Created at: April 10, 2026, 11:59 a.m.