Triple
T483026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League of European Research Universities |
E9811
|
entity |
| Predicate | language of work or name |
P15
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [League of European Research Universities, language of work or name, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: language of work or name Context triple: [League of European Research Universities, language of work or name, English]
-
A.
languageOfWorkOrName
chosen
Indicates the language in which a work is created or a name is expressed.
-
B.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
C.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
-
D.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
E.
locationOfWork
Indicates the place or site where an entity performs its work or carries out its professional activities.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0b8fe6081909f8ab87bfda6b2d8 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.