Triple
T24665522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sachem of the Mohegan |
E610663
|
entity |
| Predicate | titleLanguageFamily |
P156941
|
FINISHED |
| Object | Algonquian 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: Algonquian languages | Statement: [Sachem of the Mohegan, titleLanguageFamily, Algonquian languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleLanguageFamily Context triple: [Sachem of the Mohegan, titleLanguageFamily, Algonquian languages]
-
A.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
B.
majorLanguageFamilies
Indicates that one entity is a primary or dominant language family to which the other entity (a language or group of languages) belongs.
-
C.
coversLanguageFamily
Indicates that one entity includes or encompasses a particular language family within its scope or subject matter.
-
D.
languageOfFamily
Indicates the language or languages commonly used or associated with a particular family.
-
E.
languageFamilyOf
Indicates that one entity is the language family to which the other entity (a specific language) belongs.
- F. None of above. chosen
Provenance (4 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_69e2c4d505cc8190981881df06c0bf52 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f41011d8048190be70329ba0bfb7c7 |
completed | May 1, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69f40ed9d47881909fcfc0d04e8d074a |
completed | May 1, 2026, 2:24 a.m. |
| PDg | Predicate description generation | batch_69f41010f06c81908ee7f773220df14f |
completed | May 1, 2026, 2:29 a.m. |
Created at: April 18, 2026, 2:39 a.m.