Triple
T6025046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Davis |
E134154
|
entity |
| Predicate | helpedStandardize |
P39264
|
FINISHED |
| Object | Unicode character classification |
E26667
|
NE 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: Unicode character classification | Statement: [Mark Davis, helpedStandardize, Unicode character classification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unicode character classification Context triple: [Mark Davis, helpedStandardize, Unicode character classification]
-
A.
Unicode Character Database
chosen
The Unicode Character Database is a comprehensive collection of machine-readable data files that define the properties, classifications, and behaviors of every character encoded in the Unicode Standard.
-
B.
Grapheme_Cluster_Break
Grapheme_Cluster_Break is a Unicode text segmentation property used to determine how sequences of code points form user-perceived characters (grapheme clusters) for operations like cursor movement and text selection.
-
C.
Unicode
Unicode is a universal character encoding standard that assigns unique code points to virtually all written scripts, symbols, and emojis used in modern computing.
-
D.
Unicode Technical Standard #35
Unicode Technical Standard #35 is a Unicode Consortium specification that defines the Locale Data Markup Language (LDML) and related mechanisms for internationalization, including formatting of dates, times, numbers, and other locale-sensitive data.
-
E.
Unicode Technical Standard #10
Unicode Technical Standard #10 is the specification that defines the Unicode Collation Algorithm, providing a standardized method for comparing and sorting Unicode text across languages and platforms.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0560bae148190ad4755defaaf471b |
completed | March 22, 2026, 8:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11375b4448190ad3087b21ac67329 |
completed | March 23, 2026, 10:18 a.m. |
Created at: March 22, 2026, 4:07 p.m.