Triple
T19363987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundee derby |
E484352
|
entity |
| Predicate | languageOfLocalSupport |
P11734
|
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: [Dundee derby, languageOfLocalSupport, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfLocalSupport Context triple: [Dundee derby, languageOfLocalSupport, English]
-
A.
languageOfLocalization
Indicates the language into which something (such as software, content, or an interface) has been localized for use or display.
-
B.
languageProvision
chosen
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
C.
languageOfLocalOrganization
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
D.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
E.
serviceBranchLanguage
Indicates the language or languages used or officially recognized by a particular branch of a service (such as a military or organizational branch).
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a9ac68819082cf9deadf526156 |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:34 p.m.