Triple
T24931589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic Finnic peoples |
E619001
|
entity |
| Predicate | speakLanguageBranch |
P92545
|
FINISHED |
| Object | Finnic languages |
—
|
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: Finnic languages | Statement: [Baltic Finnic peoples, speakLanguageBranch, Finnic languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speakLanguageBranch Context triple: [Baltic Finnic peoples, speakLanguageBranch, Finnic languages]
-
A.
serviceBranchLanguage
Indicates the language or languages used or officially recognized by a particular branch of a service (such as a military or organizational branch).
-
B.
languageBranch
Indicates that one language belongs to, or is classified under, a broader linguistic branch or subgroup.
-
C.
possibleLanguageBranch
Indicates that one entity may belong to, derive from, or be classified under the language branch represented by the other entity, without asserting this relationship as certain.
-
D.
languageGroupSpoken
chosen
Indicates that a particular language group is spoken or used for communication by an entity.
-
E.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:30 a.m.