Triple
T23505936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galo language |
E572280
|
entity |
| Predicate | hasTypologicalOrder |
P1249
|
FINISHED |
| Object | SOV |
—
|
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: SOV | Statement: [Galo language, hasTypologicalOrder, SOV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypologicalOrder Context triple: [Galo language, hasTypologicalOrder, SOV]
-
A.
hasTypologicalRelation
Indicates a relationship where two linguistic entities are connected based on shared structural or typological features, such as word order, morphology, or phonological patterns.
-
B.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
C.
hasBasicWordOrder
chosen
Indicates the typical sequence in which core sentence elements (such as subject, verb, and object) are ordered in a language.
-
D.
isOrderOf
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
-
E.
hasOrderlinessProperty
Indicates that something possesses a characteristic related to order, organization, or structured arrangement.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a9009ca081908c4cffb8c32293ec |
completed | April 29, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:07 p.m.