Triple
T3558805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washo language |
E75283
|
entity |
| Predicate | hasNounIncorporation |
P50349
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Washo language, hasNounIncorporation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNounIncorporation Context triple: [Washo language, hasNounIncorporation, yes]
-
A.
hasAnaphora
Indicates that one expression in a text refers back to another earlier expression for its interpretation.
-
B.
incorporatedAs
Indicates that an organization has been legally formed and registered under a specific corporate structure or name.
-
C.
hasNounEnding
Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
-
D.
incorporatedThrough
Indicates that one entity was formed, established, or legally created by means of another specified process, mechanism, or intermediary entity.
-
E.
hasNounClassSystem
Indicates that an entity possesses a grammatical system in which nouns are categorized into distinct classes that affect their agreement with other elements in the language.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0881d50819092332491b9527c9d |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:20 p.m.