Triple
T31594831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolane language |
E806192
|
entity |
| Predicate | usesRootAndPatternMorphology |
P33904
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Wolane language, usesRootAndPatternMorphology, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRootAndPatternMorphology Context triple: [Wolane language, usesRootAndPatternMorphology, true]
-
A.
hasMorphologicalPattern
Indicates that one entity exhibits or follows a specific morphological pattern defined or associated with another entity.
-
B.
hasRootWord
chosen
Indicates that one linguistic form is derived from, based on, or directly associated with a specified root word.
-
C.
etymologicalPattern
Indicates a relationship where one form or set of forms follows a recurring etymological structure or transformation pattern derived from another.
-
D.
hasMorphosyntacticBasis
Indicates that one linguistic element’s form or syntactic behavior is grounded in, derived from, or systematically determined by another element’s morphosyntactic properties.
-
E.
usesAffixation
Indicates that one entity forms or modifies another by adding affixes (such as prefixes, suffixes, infixes, or circumfixes) to it.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 30, 2026, 10:30 p.m.