Triple
T5665788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Frisian |
E124852
|
entity |
| Predicate | primarySourcesRegion |
P410
|
FINISHED |
| Object | Frisian coastal areas |
—
|
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: Frisian coastal areas | Statement: [Old Frisian, primarySourcesRegion, Frisian coastal areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySourcesRegion Context triple: [Old Frisian, primarySourcesRegion, Frisian coastal areas]
-
A.
sourceRegion
chosen
Indicates the geographic or spatial region from which something originates or is derived.
-
B.
primaryRegionOfPopularity
Indicates the geographic region where something is most widely used, favored, or popular compared to other regions.
-
C.
studiesRegion
Indicates that an entity engages in the academic or systematic study of a particular geographic or cultural region.
-
D.
mediaCoverageRegion
Indicates the geographic area or region within which a particular piece of media or media outlet provides coverage or is intended to reach.
-
E.
placeRegion
Indicates that a place is located within, or is part of, a larger geographic or administrative 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_69c00828906881908966f270b8f130cf |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:43 p.m.