Triple
T9561809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisieux |
E230690
|
entity |
| Predicate | historicalPeople |
P34335
|
FINISHED |
| Object | Lexovii |
E720533
|
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: Lexovii | Statement: [Lisieux, historicalPeople, Lexovii]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lexovii Context triple: [Lisieux, historicalPeople, Lexovii]
-
A.
Lexovii
chosen
The Lexovii were an ancient Gallic tribe of northwestern France, known from Roman accounts for resisting Julius Caesar’s conquest of Armorica.
-
B.
Latreillius
Latreillius is a genus of crustaceans named in honor of the French zoologist and entomologist Pierre André Latreille.
-
C.
Landericus
Landericus is a Latinized variant of the given name Landry, historically used in medieval European contexts.
-
D.
Avidii
The Avidii were an ancient Roman family (gens) to which the 2nd-century usurper emperor Avidius Cassius belonged.
-
E.
Laelianus
Laelianus was a short-lived usurper emperor of the breakaway Gallic Empire in the 3rd century Roman crisis.
- 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994d31e08190b139f5ad10d8ea31 |
completed | April 1, 2026, 10:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d152a014a48190925d52967e1fbffe |
completed | April 4, 2026, 6:04 p.m. |
Created at: March 30, 2026, 8:03 p.m.