Triple
T33942872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pamunkey |
E870211
|
entity |
| Predicate | ethnoLanguageFamily |
P107565
|
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: [Pamunkey, ethnoLanguageFamily, Algonquian languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnoLanguageFamily Context triple: [Pamunkey, ethnoLanguageFamily, Algonquian languages]
-
A.
majorLanguageFamilies
Indicates that one entity is a primary or dominant language family to which the other entity (a language or group of languages) belongs.
-
B.
inLanguageFamily
Indicates that two languages belong to the same linguistic family or classification.
-
C.
ethnonymLanguageFamily
chosen
Indicates a relationship where an ethnonym is associated with the language family traditionally spoken or linked to that ethnic group.
-
D.
coversLanguageFamily
Indicates that one entity includes or encompasses a particular language family within its scope or subject matter.
-
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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.