Triple
T2806864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colva Beach |
E54072
|
entity |
| Predicate | hasSecondaryLanguageInArea |
P9103
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Colva Beach, hasSecondaryLanguageInArea, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryLanguageInArea Context triple: [Colva Beach, hasSecondaryLanguageInArea, English]
-
A.
hasSecondaryLanguage
chosen
Indicates that an entity possesses or uses a secondary language in addition to its primary language.
-
B.
isBilingualRegion
Indicates that a region officially uses two languages or has two predominant languages in regular use.
-
C.
primaryLanguageSide2
Indicates that the second entity in the relationship uses or is associated with the primary language specified.
-
D.
secondLanguageSpeakers
Indicates that the referenced language is spoken as a second (non-native) language by the specified group or number of people.
-
E.
hasNeighboringLanguages
Indicates that two languages are geographically or regionally adjacent to each other in their areas of use.
- 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_69ab49dcee188190b5c6eca9ae9e3469 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:59 p.m.