Triple
T441030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British English |
E10113
|
entity |
| Predicate | hasSpellingStandard |
P3085
|
FINISHED |
| Object | British spelling |
—
|
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: British spelling | Statement: [British English, hasSpellingStandard, British spelling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpellingStandard Context triple: [British English, hasSpellingStandard, British spelling]
-
A.
hasStandardPronunciationBasedOn
Indicates that one entity’s standard or canonical pronunciation is determined or derived from another entity’s pronunciation.
-
B.
hasStandardOrthographySince
Indicates that a language or writing system has used a particular standardized orthography starting from a specified point in time.
-
C.
hasVariantSpelling
Indicates that one term is an alternative spelling form of another term.
-
D.
hasOfficialOrthography
chosen
Indicates that an entity has a formally recognized and standardized system for writing its language or name.
-
E.
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.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef2af84881909635ebbbb3465b1b |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddcf50c8190bfa0d1f8ee9f604a |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.