Triple
T4149279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsimshianic languages |
E89863
|
entity |
| Predicate | possibleRelation |
P42547
|
FINISHED |
| Object | sometimes grouped in Penutian hypotheses |
—
|
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: sometimes grouped in Penutian hypotheses | Statement: [Tsimshianic languages, possibleRelation, sometimes grouped in Penutian hypotheses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleRelation Context triple: [Tsimshianic languages, possibleRelation, sometimes grouped in Penutian hypotheses]
-
A.
possibleRelative
chosen
Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
-
B.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
C.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.