Triple
T18978925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthonij |
E464369
|
entity |
| Predicate | isRegionalSpelling |
P108665
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Anthonij, isRegionalSpelling, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRegionalSpelling Context triple: [Anthonij, isRegionalSpelling, yes]
-
A.
spellingStyle
Indicates the particular orthographic convention or system of spelling that is used or preferred in a given context.
-
B.
usesStandardOrthographyOf
Indicates that one entity writes or represents language according to the standard orthographic system defined for another entity.
-
C.
isRegional
chosen
Indicates that something pertains to, is characteristic of, or is limited to a specific geographic region or area.
-
D.
usesRegionalStyle
Indicates that one entity employs or applies a style, method, or convention characteristic of a particular geographic region in relation to another entity or context.
-
E.
hasRegionalVariationsIn
Indicates that something exhibits different forms, versions, or characteristics depending on the geographic region.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d621e3e08190b2d1d969ecaa380b |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.