Triple
T1730437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Godolphin, Cornwall |
E37796
|
entity |
| Predicate | languageHeritage |
P11719
|
FINISHED |
| Object | Cornish language toponymy |
—
|
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: Cornish language toponymy | Statement: [Godolphin, Cornwall, languageHeritage, Cornish language toponymy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageHeritage Context triple: [Godolphin, Cornwall, languageHeritage, Cornish language toponymy]
-
A.
heritageLanguage
Indicates that one entity is the ancestral or culturally inherited language associated with another entity.
-
B.
languageDiversity
Indicates the degree to which multiple distinct languages are present and used within a given context or population.
-
C.
isCulturalLanguageOf
Indicates that a language serves as a primary medium of cultural expression, identity, and heritage for a particular group, community, or region.
-
D.
hasLinguisticHeritage
chosen
Indicates that one entity possesses or is associated with the linguistic background, tradition, or ancestry of another entity.
-
E.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
- 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_69a8861cc6ac8190ac0b2e31ccf62851 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab5c553e508190b0f511b05e07fa20 |
completed | March 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69aa61c25a648190892de94c997fb983 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.