Triple
T31595018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italo-Albanesi |
E806196
|
entity |
| Predicate | nativeLanguageAutonym |
P70102
|
FINISHED |
| Object | arbërisht |
—
|
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: arbërisht | Statement: [Italo-Albanesi, nativeLanguageAutonym, arbërisht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nativeLanguageAutonym Context triple: [Italo-Albanesi, nativeLanguageAutonym, arbërisht]
-
A.
autonymLanguageCode
Indicates that the associated language code is the one used by a language to refer to itself (its autonym).
-
B.
autonymLanguageFamily
Indicates that a language’s self-designated name (autonym) belongs to or is classified within a particular language family.
-
C.
nativeLanguage
Indicates the language that a person or entity originally learned and uses as their primary or first language.
-
D.
hasEndonymLanguage
chosen
Indicates that the language specified is the one in which a name or term is expressed in its own native or local form.
-
E.
hasEndonym
Indicates that an entity has a name or designation used by native speakers or within its own local language or community.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a83460188190a201e67b786198a4 |
completed | May 3, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:30 p.m.