Triple
T3039415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haketia |
E83088
|
entity |
| Predicate | hasPrimaryWordOrder |
P1249
|
FINISHED |
| Object | SVO |
—
|
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: SVO | Statement: [Haketia, hasPrimaryWordOrder, SVO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryWordOrder Context triple: [Haketia, hasPrimaryWordOrder, SVO]
-
A.
hasBasicWordOrder
chosen
Indicates the typical sequence in which core sentence elements (such as subject, verb, and object) are ordered in a language.
-
B.
hasV2WordOrder
Indicates that a clause or language follows verb-second (V2) word order, where the finite verb consistently appears in the second position of the sentence.
-
C.
primaryGrammaticalBasis
Indicates that one element serves as the main grammatical foundation or core structure upon which another linguistic element is based or constructed.
-
D.
hasFirstWordOfExpandedForm
Indicates that one entity is the first word in the fully expanded (non-abbreviated) form of another entity.
-
E.
usesPostpositions
Indicates that one entity employs postpositions, placing relational or grammatical markers after the words they modify rather than before them.
- 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_69ad8b2298908190a7cb4e9bdbf064d0 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9b2fa52c8190a7860f762d5232ab |
completed | March 8, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_69ad961fc62c819087c4c3a44b00847d |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.