Triple
T15339942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solano language |
E366762
|
entity |
| Predicate | linguisticDataType |
P50225
|
FINISHED |
| Object | word lists |
—
|
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: word lists | Statement: [Solano language, linguisticDataType, word lists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticDataType Context triple: [Solano language, linguisticDataType, word lists]
-
A.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
-
B.
hasLinguisticDataType
chosen
Indicates that something is associated with or characterized by a specific type or category of linguistic data.
-
C.
linguisticClassification
Indicates the relationship by which an entity is categorized according to its language or linguistic type.
-
D.
linguisticFeature
Indicates a relationship where a linguistic property, pattern, or characteristic is attributed to or associated with a language-related entity (such as a word, phrase, or text).
-
E.
linguisticField
Indicates that something pertains to or is associated with a particular area or subdiscipline within linguistics.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e12eb7c8190944a260aa1aa9156 |
completed | April 16, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69deca9659f48190b8661df223ce5078 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:17 a.m.