Triple
T28593315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Persian Wiktionary |
E723711
|
entity |
| Predicate | supportsScripts |
P150428
|
FINISHED |
| Object | Persian script |
—
|
NE NERFINISHED |
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 script | Statement: [Persian Wiktionary, supportsScripts, Persian script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsScripts Context triple: [Persian Wiktionary, supportsScripts, Persian script]
-
A.
supportsScriptVariant
Indicates that one entity is capable of handling, rendering, or operating with a particular variant of a script or writing system associated with another entity.
-
B.
scriptSupport
Indicates that one entity provides or enables scripting capabilities or support for another entity.
-
C.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
D.
usesScriptFor
chosen
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
E.
supportsJavaScriptAPIs
Indicates that one entity provides or is compatible with JavaScript-based application programming interfaces for use by 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01203ac018819085d7c9abd8345b23 |
completed | May 11, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_6a011f3f149c819090749722da0e3413 |
completed | May 11, 2026, 12:13 a.m. |
Created at: April 28, 2026, 4:21 a.m.