Triple
T19443078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antoine Laumet |
E486399
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Antoine |
—
|
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: Antoine | Statement: [Antoine Laumet, givenName, Antoine]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Antoine Context triple: [Antoine Laumet, givenName, Antoine]
-
A.
Antoine
Antoine is the given name of French naval officer and explorer Bruni d’Entrecasteaux, known for leading late 18th-century Pacific expeditions.
-
B.
Antoine
Antoine is the given name of Antoine de la Mothe Cadillac, the French explorer and founder of Detroit.
-
C.
Antoine
Antoine is the given name of the French painter and lithographer Carle Vernet, known for his depictions of horses, battles, and Napoleonic campaigns.
-
D.
Antoine
chosen
Antoine is a French given name, historically common in Francophone countries and borne by numerous notable figures in politics, arts, and science.
-
E.
Antoine
Antoine was a medieval French nobleman who held the title of Duke of Brabant in the early 15th century.
- 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63386c520819092bea5d7f259a226 |
completed | April 20, 2026, 2:09 p.m. |
Created at: April 10, 2026, 1:38 p.m.