Triple
T15873750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | རྫོང་ཁ |
E384893
|
entity |
| Predicate | derivedFromScript |
P35094
|
FINISHED |
| Object | classical Tibetan 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: classical Tibetan script | Statement: [རྫོང་ཁ, derivedFromScript, classical Tibetan script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: derivedFromScript Context triple: [རྫོང་ཁ, derivedFromScript, classical Tibetan script]
-
A.
usesScriptDerivedFrom
chosen
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by another entity.
-
B.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
C.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
-
D.
scriptOfOrigin
Indicates that one entity is the original writing system or script from which another script is derived or historically originates.
-
E.
relatedToScript
Indicates a general association or connection between an entity and a script, without specifying the exact nature of that relationship.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.