Triple
T38315762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tai Khamyang |
E1033820
|
entity |
| Predicate | currentScriptUsed |
P22941
|
FINISHED |
| Object | Assamese 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: Assamese script | Statement: [Tai Khamyang, currentScriptUsed, Assamese script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentScriptUsed Context triple: [Tai Khamyang, currentScriptUsed, Assamese script]
-
A.
scriptUsedCurrently
chosen
Indicates that a particular writing system or script is the one presently in use for a given language, text, or context.
-
B.
usesScriptFor
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
C.
laterUsedScript
Indicates that one entity adopted or employed the script of another entity at a later point in time.
-
D.
scriptName
Indicates the name or title of a script associated with an entity, typically identifying which script is used, referenced, or executed in a given context.
-
E.
scriptUsedForLanguage
Indicates that a particular writing script is employed to write or represent a given language.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffde9263248190996f970b6cf6e49d |
completed | May 10, 2026, 1:25 a.m. |
| PD | Predicate disambiguation | batch_69ffdd760f1c8190abc6c0c1cd97ba5f |
completed | May 10, 2026, 1:20 a.m. |
Created at: May 3, 2026, 4:30 p.m.