Triple
T28407656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goënga |
E719577
|
entity |
| Predicate | hasRecognizedRegionalLanguage |
P2982
|
FINISHED |
| Object | West Frisian |
—
|
NE NERFINISHED |
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: West Frisian | Statement: [Goënga, hasRecognizedRegionalLanguage, West Frisian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecognizedRegionalLanguage Context triple: [Goënga, hasRecognizedRegionalLanguage, West Frisian]
-
A.
recognizedRegionalLanguage
chosen
Indicates that a language holds officially recognized status within a specific region or subnational jurisdiction.
-
B.
recognizedLanguage
Indicates that an entity has identified, detected, or acknowledged a particular language as being used or present.
-
C.
hasLanguageRegionContext
Indicates that something is associated with or situated within a specific linguistic or language-region context.
-
D.
hasTraditionalLanguageRegion
Indicates the geographic region traditionally associated with the use or origin of a particular language.
-
E.
recognizesRegion
Indicates that one entity formally acknowledges or accepts the status, existence, or boundaries of a particular 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: April 28, 2026, 1:24 a.m.