Triple
T12088005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fanny |
E287859
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Fani |
E880285
|
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: Fani | Statement: [Fanny, hasVariant, Fani]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fani Context triple: [Fanny, hasVariant, Fani]
-
A.
Fani
chosen
Fani is a diminutive given name derived from Theophania, commonly used as a familiar or affectionate form of that name.
-
B.
Ferminia
Ferminia is a small genus of wrens in the family Troglodytidae, best known for the critically endangered Cuban endemic species Ferminia cerverai (the Zapata wren).
-
C.
Sheilia
Sheilia is a feminine given name, typically considered an alternative spelling of the name Sheila.
-
D.
Marianna
Marianna is a small city in Florida’s Panhandle known for its historic architecture, including the Russ House, and its proximity to natural attractions like caves and springs.
-
E.
Nannini
Nannini is an Italian surname most prominently associated with rock singer-songwriter Gianna Nannini and her family.
- 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_69d6ab4964708190850585628b287b0c |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91514c78c8190bc1cd569e524e8b4 |
completed | April 10, 2026, 3:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f668eff88190877ce9bb991c1258 |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.