Triple
T3558800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washo language |
E75283
|
entity |
| Predicate | hasAspectMarking |
P2130
|
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, hasAspectMarking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAspectMarking Context triple: [Washo language, hasAspectMarking, yes]
-
A.
hasAspectSystem
Indicates that an entity possesses or is associated with a particular aspect system, such as a structured set of characteristics, dimensions, or perspectives.
-
B.
hasKeyAspect
Indicates that something possesses a central, defining, or particularly important feature or characteristic.
-
C.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
D.
hasCaseMarking
Indicates that a linguistic element (such as a noun or pronoun) bears a specific grammatical case marking that signals its syntactic or semantic role in a clause.
-
E.
refersToAspect
Indicates that one entity specifically references or points to a particular aspect, feature, or component of another entity.
- 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_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. |
Created at: March 8, 2026, 3:20 p.m.