Triple
T7309927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pashto alphabet |
E168064
|
entity |
| Predicate | hasBaseScript |
P58736
|
FINISHED |
| Object | Arabic script |
—
|
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: Arabic script | Statement: [Pashto alphabet, hasBaseScript, Arabic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBaseScript Context triple: [Pashto alphabet, hasBaseScript, Arabic script]
-
A.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
B.
hasBaseSystem
chosen
Indicates that one entity is founded upon, derived from, or primarily operates using another entity as its underlying system or framework.
-
C.
hasScriptRegulator
Indicates that an entity has an associated mechanism or component that controls or governs its script or scripting behavior.
-
D.
hasSupportBase
Indicates that one entity serves as the supporting base or foundation upon which another entity rests, is mounted, or is structurally stabilized.
-
E.
hasSupportBaseIn
Indicates that one entity maintains an operational or organizational base of support located in another entity.
- 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.