Triple
T20146212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korku |
E491308
|
entity |
| Predicate | subjectObjectVerbOrder |
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: [Korku, subjectObjectVerbOrder, SOV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectObjectVerbOrder Context triple: [Korku, subjectObjectVerbOrder, SOV]
-
A.
objectOfVerb
Indicates that one entity serves as the direct object or recipient of the action expressed by a given verb in a clause.
-
B.
alsoExhibitsWordOrder
Indicates that one linguistic element displays the same or an additional word order pattern as another element or construction.
-
C.
hasSubjectPosition
Indicates that an entity occupies or is assigned to a particular subject role or position within a structure, context, or organization.
-
D.
usesPostpositions
Indicates that one entity employs postpositions, placing relational or grammatical markers after the words they modify rather than before them.
-
E.
hasBasicWordOrder
chosen
Indicates the typical sequence in which core sentence elements (such as subject, verb, and object) are ordered in a 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6679e43a48190b3a5da5710b07ff7 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:33 p.m.