Triple
T9052013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 3.0 |
E216905
|
entity |
| Predicate | addsCharactersOverUnicode2.1 |
P47136
|
FINISHED |
| Object | 10493 |
—
|
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: 10493 | Statement: [Unicode 3.0, addsCharactersOverUnicode2.1, 10493]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsCharactersOverUnicode2.1 Context triple: [Unicode 3.0, addsCharactersOverUnicode2.1, 10493]
-
A.
providesAdditionalCharactersFor
Indicates that one entity supplies extra or supplementary characters to be used by another entity or process.
-
B.
encodedInUnicodeSince
Indicates that a given character or symbol has been included and assigned a code point in the Unicode standard starting from a specific version or time.
-
C.
addsCharactersCount
chosen
Indicates that one entity increases the number of characters (e.g., text length) in another entity by a specified amount.
-
D.
hasAdditionalUnicodeBlock
Indicates that an entity is associated with one or more supplementary Unicode character blocks beyond its primary assigned block.
-
E.
hasUnicode
Indicates that an entity is associated with, represented by, or encoded using a specific Unicode character or sequence.
- 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc7a700de48190aa9f61d850e01cbd |
completed | April 1, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:10 p.m.