Triple
T34021157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gāhā Sattasaī |
E872384
|
entity |
| Predicate | scriptOriginallyUsed |
P150428
|
FINISHED |
| Object | Brāhmī-derived scripts |
—
|
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: Brāhmī-derived scripts | Statement: [Gāhā Sattasaī, scriptOriginallyUsed, Brāhmī-derived scripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOriginallyUsed Context triple: [Gāhā Sattasaī, scriptOriginallyUsed, Brāhmī-derived scripts]
-
A.
scriptOfOrigin
Indicates that one entity is the original writing system or script from which another script is derived or historically originates.
-
B.
scriptSource
Indicates that one entity is the origin or provider of the script used or referenced by another entity.
-
C.
usesScriptFor
chosen
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
D.
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.
-
E.
laterUsedScript
Indicates that one entity adopted or employed the script of another entity at a later point in time.
- 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_69f349a19ad88190ab586f010c804a8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:51 a.m.