Triple
T15410097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisa Quenu |
E368564
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Quenu |
E1145595
|
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: Quenu | Statement: [Lisa Quenu, spouse, Quenu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Quenu Context triple: [Lisa Quenu, spouse, Quenu]
-
A.
Quenu
chosen
Quenu is a French surname most notably associated with Pauline Quenu.
-
B.
Qwaraña
Qwaraña is an alternative name for the Qwara language, a lesser-known Afroasiatic language historically spoken by the Beta Israel (Ethiopian Jewish) community in Ethiopia.
-
C.
Quaama
Quaama is a small rural village in New South Wales, Australia, situated within the Bega Valley region.
-
D.
Qene
Qene is a traditional form of improvised, metaphor-rich religious poetry central to Eritrean and Ethiopian Orthodox Christian worship and scholarship.
-
E.
Echenique
Echenique is a Spanish-language surname of Basque origin borne by various notable figures in politics, arts, and public life across the Spanish-speaking world.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea4f13c819085d26fd32b5dca6f |
completed | April 16, 2026, 1:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff135d65988190b35392bdf1e45985 |
completed | May 9, 2026, 10:58 a.m. |
Created at: April 10, 2026, 3:20 a.m.