Triple
T7873948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fa d’Ambô |
E182804
|
entity |
| Predicate | closelyRelatedTo |
P37
|
FINISHED |
| Object | Angolar |
E94969
|
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: Angolar | Statement: [Fa d’Ambô, closelyRelatedTo, Angolar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Angolar Context triple: [Fa d’Ambô, closelyRelatedTo, Angolar]
-
A.
Angolar
chosen
Angolar is a Portuguese-based creole language spoken primarily by the Angolar community on the island of São Tomé in São Tomé and Príncipe.
-
B.
Anglona
Anglona is a historical and geographical subregion in northern Sardinia, Italy, known for its rural landscapes, medieval villages, and traditional Sardinian culture.
-
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.
Angi
Angi is a digital marketplace that connects homeowners with local contractors and service professionals for home improvement and repair projects.
-
E.
Agno
Agno is a small Swiss town in the canton of Ticino, known for its lakeside location, regional airport, and proximity to Lugano.
- 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_69ca828a17248190b46defe758bc5ad3 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb39a7f1648190980db4db1a800189 |
completed | March 31, 2026, 3:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5b79705c8190955e128081048ebe |
completed | March 31, 2026, 5:28 a.m. |
Created at: March 30, 2026, 4:56 p.m.