Triple
T22983615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint Vaast |
E571537
|
entity |
| Predicate | associatedWith |
P37
|
FINISHED |
| Object | King Clovis I |
—
|
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: King Clovis I | Statement: [Saint Vaast, associatedWith, King Clovis I]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: King Clovis I Context triple: [Saint Vaast, associatedWith, King Clovis I]
-
A.
Chlothar I
Chlothar I was a 6th-century Merovingian king of the Franks who eventually reunited the Frankish kingdom under his sole rule.
-
B.
Clovis II
Clovis II was a 7th-century Merovingian king of Neustria and Burgundy, known for his weak rule under the dominance of powerful nobles and mayors of the palace.
-
C.
King Childebert I
King Childebert I was a 6th-century Merovingian ruler of Paris and Orléans, known for his military campaigns, territorial expansion, and role in consolidating the Frankish kingdom.
-
D.
Clovis
chosen
Clovis is a masculine given name of Germanic origin, historically associated with early Frankish kings and related to names like Louis and Ludwig.
-
E.
Clovis
Clovis is a small city in eastern New Mexico known as a regional hub for agriculture, rail transport, and nearby Cannon Air Force Base.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829775e881909c5d6d35d3fd57f7 |
completed | April 29, 2026, 4:01 a.m. |
Created at: April 17, 2026, 3:49 p.m.