Triple
T7909632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonino Giovanni Ribisi |
E183663
|
entity |
| Predicate | hasGivenNameInLanguage |
P21937
|
FINISHED |
| Object | Antonino@it |
—
|
LITERAL 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: Antonino@it | Statement: [Antonino Giovanni Ribisi, hasGivenNameInLanguage, Antonino@it]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenNameInLanguage Context triple: [Antonino Giovanni Ribisi, hasGivenNameInLanguage, Antonino@it]
-
A.
hasNameInLocalLanguage
chosen
Indicates that an entity is associated with a name expressed in the local or native language of a given context or region.
-
B.
hasFamilyNameInLanguage
Indicates that an entity has a specific family name as expressed or written in a particular language.
-
C.
hasFullNameLanguage
Indicates that the language in which a full name is expressed is associated with that full name.
-
D.
hasEthnologueName
Indicates that an entity is associated with a specific language name as recorded in the Ethnologue reference.
-
E.
hasGivenNameBasis
Indicates that one entity’s given name is derived from, based on, or formed using another entity (such as a name, word, or person) as its basis.
- F. None of above.
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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a5c85ac81908de2ca387826ea2f |
completed | March 31, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69cae92f9498819085277879e59aa072 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:03 p.m.