Triple
T16801034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terioki |
E408352
|
entity |
| Predicate | hasHistoricalLanguageCommunity |
P36041
|
FINISHED |
| Object | Finnish speakers |
—
|
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: Finnish speakers | Statement: [Terioki, hasHistoricalLanguageCommunity, Finnish speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalLanguageCommunity Context triple: [Terioki, hasHistoricalLanguageCommunity, Finnish speakers]
-
A.
hasLanguageCommunity
Indicates that an entity is associated with or serves a particular language community.
-
B.
hasMajorityLanguageHistorically
chosen
Indicates that a particular language has historically been the predominant or majority language within a given entity or region.
-
C.
hasHistoricCommunity
Indicates that an entity is associated with, contains, or is part of a community of historical significance.
-
D.
historicalLanguageStatus
Indicates that a language had a particular official, social, or functional status during a past historical period.
-
E.
historicalLanguageCenter
Indicates that a location has served as a significant hub or focal point for the development, use, or study of a particular language in the past.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2c826808190aa0a5bfcde2e49a8 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e319d0fdb8819088425bd82431640f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.