Triple
T3063311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJUE |
E62045
|
entity |
| Predicate | workingLanguages |
P35567
|
FINISHED |
| Object | all official languages of the European Union |
—
|
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: all official languages of the European Union | Statement: [CJUE, workingLanguages, all official languages of the European Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingLanguages Context triple: [CJUE, workingLanguages, all official languages of the European Union]
-
A.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
B.
areSpokenIn
Indicates that a particular language is used as a spoken means of communication within a specified region, community, or context.
-
C.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
D.
hasLanguages
chosen
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
E.
languageOfReleases
Indicates the language in which the releases associated with an entity are produced or published.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9ea088fc819090b9d5bbcb268671 |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.