Triple
T9460886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parachi |
E228140
|
entity |
| Predicate | usesScriptDirection |
P2264
|
FINISHED |
| Object | right-to-left |
—
|
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: right-to-left | Statement: [Parachi, usesScriptDirection, right-to-left]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesScriptDirection Context triple: [Parachi, usesScriptDirection, right-to-left]
-
A.
scriptDirection
Indicates the direction in which a writing system or script is read or written (e.g., left-to-right, right-to-left, top-to-bottom).
-
B.
scriptDirectionOrigin
Indicates the original writing direction (such as left-to-right or right-to-left) from which a script’s layout or orientation is derived.
-
C.
hasWritingDirection
chosen
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
-
D.
usesScriptDerivedFrom
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by another entity.
-
E.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
- 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_69ca843b123881909b0e60028475d12d |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7fcaf610819092bcd3b871665aa5 |
completed | April 1, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69cca55caaa8819089c5138e014892d3 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:52 p.m.