Triple
T6728278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bima language |
E153570
|
entity |
| Predicate | hasPrimaryWordFormationProcess |
P73391
|
FINISHED |
| Object | affixation |
—
|
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: affixation | Statement: [Bima language, hasPrimaryWordFormationProcess, affixation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryWordFormationProcess Context triple: [Bima language, hasPrimaryWordFormationProcess, affixation]
-
A.
hasRootWord
Indicates that one linguistic form is derived from, based on, or directly associated with a specified root word.
-
B.
hasTwoWordForm
Indicates that an entity is represented or expressed using a form consisting of exactly two words.
-
C.
etymologicalForm
Indicates that one linguistic form is derived from, or historically originates in, another form as its etymological source.
-
D.
compositionalForm
Indicates the structural or formal composition that defines how parts are organized or combined within something.
-
E.
grammaticalForm
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
- F. None of above. chosen
Provenance (4 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_69c6880afb988190ad88011b48ecfcba |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d354177481908ab3cf5437c095e2 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d08e8a2c8190ae4e8d8c039be7ce |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d35134148190b49fb5c25a0f8ed4 |
completed | March 27, 2026, 6:58 p.m. |
Created at: March 27, 2026, 2:08 p.m.