Triple
T126380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italic languages |
E2559
|
entity |
| Predicate | notableDescendantLanguage |
P4268
|
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: [Italic languages, notableDescendantLanguage, Italian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDescendantLanguage Context triple: [Italic languages, notableDescendantLanguage, Italian]
-
A.
influencedLanguage
Indicates that one language has had an effect on the development, structure, or usage of another language.
-
B.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
C.
notableDescent
chosen
Indicates a genealogical relationship where one entity is a descendant of another in a way considered historically, culturally, or socially significant.
-
D.
hasLanguageOfOrigin
Indicates that one entity has its origin or source in the language specified by another entity.
-
E.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.