Triple
T16110069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tlingit people |
E390848
|
entity |
| Predicate | moiety |
P72601
|
FINISHED |
| Object | Raven moiety |
—
|
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: Raven moiety | Statement: [Tlingit people, moiety, Raven moiety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moiety Context triple: [Tlingit people, moiety, Raven moiety]
-
A.
moietySystem
chosen
Indicates a relationship where an entity is classified or organized according to a moiety system, typically dividing a society or group into two complementary social halves.
-
B.
chemicalComponent
Indicates that one entity is a constituent chemical part or ingredient of another entity.
-
C.
isomer
Indicates that two chemical species share the same molecular formula but differ in the arrangement or orientation of their atoms, resulting in distinct structures or properties.
-
D.
minorIsoform
Indicates that one biological isoform is a less prevalent or secondary variant relative to another isoform.
-
E.
reactant
Indicates that an entity participates as a starting material or input substance in a chemical or reactive process.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016665c0819081aa7a44b1d08183 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.