Triple
T4458079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King of the Franks |
E97780
|
entity |
| Predicate | typicalLatinForm |
P45453
|
FINISHED |
| Object | Rex Francorum |
—
|
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: Rex Francorum | Statement: [King of the Franks, typicalLatinForm, Rex Francorum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLatinForm Context triple: [King of the Franks, typicalLatinForm, Rex Francorum]
-
A.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
B.
dominantForm
Indicates that one form, type, or variant is the primary or most prevalent version relative to others in a given context.
-
C.
accentedFormOf
Indicates that one linguistic form is an accented or diacritically marked variant of another, more basic form.
-
D.
etymologicalForm
Indicates that one linguistic form is derived from, or historically originates in, another form as its etymological source.
-
E.
nameFormInLatin
chosen
Indicates that an entity’s name is expressed or recorded in its Latin-language form.
- 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_69b3454777808190b78aa9047ba1f018 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3564485688190a0d49fdccf8724be |
completed | March 13, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69b34f649df081909d3cc2f6a1b8f282 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:33 p.m.