Triple
T11844533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clovis |
E281739
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Luis |
unclear NED1
|
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: Luis | Statement: [Clovis, relatedName, Luis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Luis Context triple: [Clovis, relatedName, Luis]
-
A.
Luis
Luis is the Spanish given name of Louis I of Spain, an 18th-century Bourbon king who briefly ruled the country.
-
B.
Luis
Luis is a comedic supporting character in the Marvel Cinematic Universe, best known as Scott Lang’s fast-talking friend and former cellmate in the Ant-Man films.
-
C.
Luis
Luis de Velasco y Aragón was a Spanish nobleman and colonial administrator who served as Viceroy of New Spain and later of Peru in the late 17th and early 18th centuries.
-
D.
Luis
Luis was a Portuguese infante and nobleman who held the title Duke of Beja in the 16th century.
-
E.
Luis
Luis is a common Spanish given name derived from the Germanic name Ludwig, widely used across Spanish-speaking countries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d6ab287ba48190a5178779fd19b9b7 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a65b5ff08190bb58361f6a6acdca |
completed | April 10, 2026, 7:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4716d92c881908d45cb7b3babb1f7 |
completed | May 1, 2026, 9:25 a.m. |
Created at: April 8, 2026, 9:43 p.m.