Triple
T1845392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorani |
E41273
|
entity |
| Predicate | hasSOVWordOrder |
P1249
|
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: [Gorani, hasSOVWordOrder, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSOVWordOrder Context triple: [Gorani, hasSOVWordOrder, true]
-
A.
hasBasicWordOrder
chosen
Indicates the typical sequence in which core sentence elements (such as subject, verb, and object) are ordered in a language.
-
B.
hasSVOOrder
Indicates that a language or construction follows a basic word order where the subject comes first, followed by the verb, and then the object.
-
C.
hasSubjectPosition
Indicates that an entity occupies or is assigned to a particular subject role or position within a structure, context, or organization.
-
D.
hasSyllableStructure
Indicates that an entity (typically a word or morpheme) possesses a particular arrangement or pattern of syllables.
-
E.
hasNounClassSystem
Indicates that an entity possesses a grammatical system in which nouns are categorized into distinct classes that affect their agreement with other elements in the language.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdca6d8819083c66f3a29fd9fd1 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.