Triple
T15859351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luigi Longo |
E384540
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Longo |
E384540
|
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: Longo | Statement: [Luigi Longo, familyName, Longo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Longo Context triple: [Luigi Longo, familyName, Longo]
-
A.
Longo
chosen
Longo is an Italian surname borne by various notable figures in politics, arts, and sports.
-
B.
Lange
Lange is a German surname borne by numerous notable individuals across fields such as science, politics, arts, and sports.
-
C.
Longu
Longu is an Austronesian language spoken in the Solomon Islands, known primarily as a local name for the Longgu language.
-
D.
Lungro
Lungro is a town in southern Italy known as a principal center of the Italo-Albanian Catholic Church and its Arbëreshë (Albanian) cultural heritage.
-
E.
Uzun
Uzun is the sobriquet of Uzun Hasan, a 15th-century ruler of the Aq Qoyunlu confederation known for his conflicts with the Ottoman Empire and efforts to expand his realm in Anatolia and Iran.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1555a1f008190bb3f03b0f35ed8a4 |
completed | April 16, 2026, 9:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa14da7ac8190bbef49a1602a76fe |
completed | May 9, 2026, 9:04 p.m. |
Created at: April 10, 2026, 4:50 a.m.