Triple
T5275087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toba Batak language |
E119353
|
entity |
| Predicate | hasAffixType |
P61690
|
FINISHED |
| Object | prefixes |
—
|
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: prefixes | Statement: [Toba Batak language, hasAffixType, prefixes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAffixType Context triple: [Toba Batak language, hasAffixType, prefixes]
-
A.
hasAffiliationType
Indicates that one entity is connected to another through a specified kind or category of affiliation or association.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasAppellationType
Indicates that an entity’s name or title is associated with a specific category or type of appellation.
-
D.
hasNameSuffix
Indicates that an entity’s name includes a specific suffix or ending component.
-
E.
hasPrepositionalPrefix
Indicates that one entity functions as a prepositional prefix attached to or modifying another entity.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7c23bed88190b406dee21957d823 |
completed | March 20, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69bd77c83d1c8190bd8b9616113d413c |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd782108bc8190be68ccce09cfd3ef |
completed | March 20, 2026, 4:38 p.m. |
Created at: March 20, 2026, 1:51 p.m.