Triple
T1037078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtic languages |
E22386
|
entity |
| Predicate | hasLivingLanguages |
P20092
|
FINISHED |
| Object | Irish |
—
|
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: Irish | Statement: [Celtic languages, hasLivingLanguages, Irish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivingLanguages Context triple: [Celtic languages, hasLivingLanguages, Irish]
-
A.
extantLanguage
chosen
Indicates that a language currently exists or is in active use, as opposed to being extinct or only historically attested.
-
B.
isWorkingLanguageOf
Indicates that a particular language is officially used as a medium of work, communication, or operation within a specified organization, institution, or context.
-
C.
hasApproximateNumberOfLanguages
Indicates that an entity is associated with a quantity representing an estimated or non-exact count of languages.
-
D.
estimatedNumberOfLanguages
Indicates the approximate count of distinct languages associated with an entity, typically based on estimation rather than an exact measurement.
-
E.
hasNeighboringLanguages
Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.