Triple
T34311265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis III, Duke of Brittany |
E880452
|
entity |
| Predicate | royalNameNumber |
P3023
|
FINISHED |
| Object | Francis III |
—
|
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: Francis III | Statement: [Francis III, Duke of Brittany, royalNameNumber, Francis III]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalNameNumber Context triple: [Francis III, Duke of Brittany, royalNameNumber, Francis III]
-
A.
epithetOfMonarchNumber
Indicates that a particular epithet (descriptive title or nickname) is associated with a specific numbered monarch in a royal succession.
-
B.
usedAsRoyalNameOn
Indicates that something served as a royal name or title during a specified time or in a specified context.
-
C.
kingNumberWithinDynasty
Indicates the ordinal position of a king within a specific dynasty, expressing which numbered ruler he is in that dynastic sequence.
-
D.
royalHouseNameForm
Indicates the specific linguistic or formal version of a royal house’s name used in a given context.
-
E.
monarchNumber
chosen
Indicates the ordinal position or sequence number assigned to a monarch within a line of rulers.
- 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:57 a.m.