Triple
T1173212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sino-Tibetan languages |
E24959
|
entity |
| Predicate | commonWordOrder |
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: [Sino-Tibetan languages, commonWordOrder, SOV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonWordOrder Context triple: [Sino-Tibetan languages, commonWordOrder, SOV]
-
A.
hasBasicWordOrder
chosen
Indicates the typical sequence in which core sentence elements (such as subject, verb, and object) are ordered in a language.
-
B.
traditionalOrder
Indicates that entities are arranged or occur according to a customary, historically established sequence or hierarchy.
-
C.
usesPostpositions
Indicates that one entity employs postpositions, placing relational or grammatical markers after the words they modify rather than before them.
-
D.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
E.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcecab688190b21a926874cd98d1 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.