Triple
T11930034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludovic |
E283885
|
entity |
| Predicate | hasCognate |
P2525
|
FINISHED |
| Object | Clovis |
E281739
|
NE 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: Clovis | Statement: [Ludovic, hasCognate, Clovis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Clovis Context triple: [Ludovic, hasCognate, Clovis]
-
A.
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.
-
B.
Clovis
Clovis is a city in Fresno County, California, known as a gateway to the Sierra Nevada and for its historic Old Town district.
-
C.
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.
-
D.
Clovis
Clovis is a prehistoric Native American culture known for its distinctive fluted stone spear points and for representing some of the earliest widely accepted human inhabitants of North America.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90303a9a88190a4044e6310ba9b4b |
completed | April 10, 2026, 2:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4406ee910819093c72738bfe3f92c |
completed | May 1, 2026, 5:55 a.m. |
Created at: April 8, 2026, 9:45 p.m.