Triple
T2531715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samoset |
E56173
|
entity |
| Predicate | learnedEnglishFrom |
P7251
|
FINISHED |
| Object | English fishermen |
—
|
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 fishermen | Statement: [Samoset, learnedEnglishFrom, English fishermen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: learnedEnglishFrom Context triple: [Samoset, learnedEnglishFrom, English fishermen]
-
A.
englishFlagship
Indicates that an entity participates in or is associated with an English flagship program (typically an intensive, advanced English language or studies track).
-
B.
studiedUnder
chosen
Indicates that one entity received instruction, training, or mentorship from another, typically in an academic or apprenticeship context.
-
C.
languageIntroduced
Indicates that a particular language was brought into use or made known within a certain context, time, or place.
-
D.
hasLanguageOfStudy
Indicates that an entity studies or is engaged in learning a particular language.
-
E.
taughtAsForeignLanguageIn
Indicates that a language is taught as a foreign (non-native) language within a particular educational context or institution.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2781700819091ffc32244d9efe2 |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.