Triple
T548337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wales Millennium Centre |
E12780
|
entity |
| Predicate | languageFocus |
P11734
|
FINISHED |
| Object | Welsh culture |
—
|
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: Welsh culture | Statement: [Wales Millennium Centre, languageFocus, Welsh culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFocus Context triple: [Wales Millennium Centre, languageFocus, Welsh culture]
-
A.
languageShift
Indicates a change in the primary language used by an entity, such as switching from one language to another over time or in a given context.
-
B.
languageForm
Indicates the specific linguistic form or expression in which something is conveyed or represented.
-
C.
languageProvision
chosen
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use by another entity.
-
D.
languageStandard
Indicates that one entity conforms to, is defined by, or is governed by the language rules, specifications, or conventions established by another entity as a standard.
-
E.
languageBegins
Indicates that a particular language starts to be used, recognized, or becomes relevant at a specific point in time or context.
- 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_69a49334226c81908b0ea1689ef6aa3f |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49900895c819092a131c185a758bf |
completed | March 1, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69a494b957988190bc269e372df2f0b2 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.