Triple
T7309944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pashto alphabet |
E168064
|
entity |
| Predicate | includesAllLettersOf |
P7160
|
FINISHED |
| Object | Persian alphabet |
—
|
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: Persian alphabet | Statement: [Pashto alphabet, includesAllLettersOf, Persian alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAllLettersOf Context triple: [Pashto alphabet, includesAllLettersOf, Persian alphabet]
-
A.
hasLetter
Indicates that one entity contains, includes, or is associated with a specific letter or character.
-
B.
hasDistinctLettersFor
Indicates that one entity is associated with another such that the letters used in the first are all different from (i.e., share no letters with) those used in the second.
-
C.
hasLetterBy
Indicates that an entity possesses or is associated with a letter authored or sent by another entity.
-
D.
usesAlphabet
chosen
Indicates that one entity employs or is written using the alphabet or writing system associated with another entity.
-
E.
hasDistinctLetters
Indicates that all letters in the given string or word are unique, with no character repeated.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebdbd6f481908e69e53dab452656 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.