Triple
T7591852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan Celtic Festival |
E179752
|
entity |
| Predicate | linguisticScope |
P78030
|
FINISHED |
| Object | Celtic languages |
—
|
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: Celtic languages | Statement: [Pan Celtic Festival, linguisticScope, Celtic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticScope Context triple: [Pan Celtic Festival, linguisticScope, Celtic languages]
-
A.
officialLanguageScope
Indicates the scope or extent (such as region, institution, or context) within which a language holds official status.
-
B.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
-
C.
linguisticArea
Indicates a regional context in which languages share features due to geographic proximity and contact rather than common genetic origin.
-
D.
linguisticSignificance
Indicates the degree to which something is important, influential, or meaningful within a particular language or linguistic system.
-
E.
linguisticField
Indicates that something pertains to or is associated with a particular area or subdiscipline within linguistics.
- F. None of above. chosen
Provenance (4 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_69c69f335248819093c1006f30513708 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b746ac8190b255afdfb9635f72 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e04c2c8190a889d928515d9b8e |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:53 p.m.