Triple
T30861822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modern Mon |
E786079
|
entity |
| Predicate | scriptUltimatelyDerivedFrom |
P55092
|
FINISHED |
| Object | Brahmi 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: Brahmi script | Statement: [Modern Mon, scriptUltimatelyDerivedFrom, Brahmi script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptUltimatelyDerivedFrom Context triple: [Modern Mon, scriptUltimatelyDerivedFrom, Brahmi script]
-
A.
scriptDerivation
Indicates that one script is derived, adapted, or generated from another script or source.
-
B.
scriptOfOrigin
chosen
Indicates that one entity is the original writing system or script from which another script is derived or historically originates.
-
C.
derivedFrom
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
D.
usesScriptDerivedFrom
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by another entity.
-
E.
settingDerivedFrom
Indicates that one setting or configuration is obtained, inferred, or generated based on another setting or source.
- 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_69f224b91c14819084e764832fe67a57 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:47 p.m.