Triple
T3762884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidamo |
E82602
|
entity |
| Predicate | hasPrepositionsOrPostpositions |
P15729
|
FINISHED |
| Object | postpositions |
—
|
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: postpositions | Statement: [Sidamo, hasPrepositionsOrPostpositions, postpositions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrepositionsOrPostpositions Context triple: [Sidamo, hasPrepositionsOrPostpositions, postpositions]
-
A.
hasPrepositionalPrefix
Indicates that one entity functions as a prepositional prefix attached to or modifying another entity.
-
B.
usesPostpositions
chosen
Indicates that one entity employs postpositions, placing relational or grammatical markers after the words they modify rather than before them.
-
C.
hasPronounSystem
Indicates that an entity possesses or employs a particular system or set of rules for using pronouns.
-
D.
hasNounEnding
Indicates that something possesses or exhibits a particular noun-forming ending or suffix.
-
E.
hasCaseForms
Indicates that an entity possesses multiple grammatical case variants or inflected forms associated with it.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfbecf8819099d80af480cbe2d2 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04c851c8190ae5eaebf36df539b |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.