Triple
T31399725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kafir (religious term) |
E800963
|
entity |
| Predicate | hasRootForm |
P33904
|
FINISHED |
| Object | k-f-r (Arabic root) |
—
|
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: k-f-r (Arabic root) | Statement: [Kafir (religious term), hasRootForm, k-f-r (Arabic root)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRootForm Context triple: [Kafir (religious term), hasRootForm, k-f-r (Arabic root)]
-
A.
isRootFormOf
Indicates that one form of a word is the base or canonical form from which another inflected or derived form originates.
-
B.
hasRootSystem
Indicates that one entity possesses or is characterized by a particular type of root system.
-
C.
hasRootWord
chosen
Indicates that one linguistic form is derived from, based on, or directly associated with a specified root word.
-
D.
hasRootName
Indicates that an entity is associated with a fundamental or original name from which its other names or forms are derived.
-
E.
hasForm
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 29, 2026, 9:19 p.m.