Triple
T17431620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nulvi |
E423884
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | Anglona |
—
|
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: Anglona | Statement: [Nulvi, partOf, Anglona]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anglona Context triple: [Nulvi, partOf, Anglona]
-
A.
Anglona
chosen
Anglona is a historical and geographical subregion in northern Sardinia, Italy, known for its rural landscapes, medieval villages, and traditional Sardinian culture.
-
B.
Angy
Angy is a diminutive or affectionate nickname commonly used for the given name Angela.
-
C.
Anga
Anga was an ancient kingdom in the eastern Indian subcontinent, often noted in epic literature as the realm ruled by the warrior Karna.
-
D.
Ingleba
Ingleba is a small locality situated within the New England North West region of New South Wales, Australia.
-
E.
Óengusa
Óengusa is an Old Irish personal name, historically borne by early medieval Gaelic figures and preserved in various patronymic forms.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4490072b48190a39b1ac7bb5eb035 |
completed | April 19, 2026, 3:16 a.m. |
Created at: April 10, 2026, 5:46 a.m.