Triple
T18133519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Livio Borghese |
E434076
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Livio |
—
|
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: Livio | Statement: [Livio Borghese, givenName, Livio]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Livio Context triple: [Livio Borghese, givenName, Livio]
-
A.
Livio
chosen
Livio is an Italian masculine given name of Latin origin, commonly used in Italy and other Romance-language countries.
-
B.
Livias
Livias was an ancient town in the region of Perea, east of the Jordan River, known from classical and biblical-era sources.
-
C.
Faetano
Faetano is one of the nine municipalities (castelli) of San Marino, a small enclave known for its historic character and position in the country’s southeastern area.
-
D.
Tullio
Tullio is an Italian given name most famously borne by the mathematician Tullio Levi-Civita, known for his work in tensor calculus and differential geometry.
-
E.
Leo Calini
Leo Calini was an Italian architect known for his work on major public infrastructure projects, including the design of Rome’s central railway hub, Roma Termini.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de04321c81909c0b9d47757720fd |
completed | April 19, 2026, 1:52 p.m. |
Created at: April 10, 2026, 10:29 a.m.