Triple
T2980991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mem |
E80508
|
entity |
| Predicate | finalFormLettersSet |
P17610
|
FINISHED |
| Object | Kaf sofit |
—
|
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: Kaf sofit | Statement: [Mem, finalFormLettersSet, Kaf sofit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalFormLettersSet Context triple: [Mem, finalFormLettersSet, Kaf sofit]
-
A.
hasFinalFormLetters
chosen
Indicates that certain letters in a script change to a distinct "final" shape when they appear at the end of a word.
-
B.
standardFormUsedIn
Indicates that a particular standard form is employed or applied within a given context, process, or system.
-
C.
isFormalizedBy
Indicates that something is given a defined, structured, or official form through a specific method, process, or representation.
-
D.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
E.
formedTo
Indicates that one entity was created, established, or organized for the purpose of serving, supporting, or enabling another entity or activity.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad999e91788190a2d430dd0600a660 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.