Triple
T28886369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayah Li script |
E732570
|
entity |
| Predicate | yearUnicodeIntroduced |
P87638
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Kayah Li script, yearUnicodeIntroduced, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearUnicodeIntroduced Context triple: [Kayah Li script, yearUnicodeIntroduced, 2008]
-
A.
UnicodeStandardVersionIntroduced
Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
-
B.
addedToUnicodeYear
chosen
Indicates the year in which a given character or symbol was officially incorporated into the Unicode Standard.
-
C.
UnicodeBlock
Indicates that a character belongs to a specific contiguous range of code points defined as a Unicode block.
-
D.
UnicodeCodePointStandard
Indicates that a Unicode code point conforms to, or is defined within, a particular Unicode standard or version.
-
E.
unicodeRangeStart
Indicates the starting code point in Unicode for a specified range of characters or symbols.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65a718b288190bfcae9fddf71aced |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:50 a.m.