Triple
T26045732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Capurrius |
E647823
|
entity |
| Predicate | hasOriginalLanguageOfBaseName |
P28203
|
FINISHED |
| Object | Italian |
—
|
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: Italian | Statement: [Capurrius, hasOriginalLanguageOfBaseName, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalLanguageOfBaseName Context triple: [Capurrius, hasOriginalLanguageOfBaseName, Italian]
-
A.
originalNameLanguage
chosen
Indicates that the specified language is the language in which an entity’s original or primary name was expressed.
-
B.
hasAlternativeNameOfParentLanguage
Indicates that an entity has an alternative or variant name derived from or associated with the name of its parent language.
-
C.
hasBaseNameMeaning
Indicates that an entity’s base name carries or is associated with a particular meaning.
-
D.
hasOriginalNameOf
Indicates that one entity is the original or earlier name from which another entity’s current or later name is derived.
-
E.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
- 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_69e77e8d419481908004e6318d28aaab |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 22, 2026, 9:10 a.m.