Triple
T27524845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 3.2 |
E694805
|
entity |
| Predicate | addsCharactersTo |
P84686
|
FINISHED |
| Object | Unicode Standard |
—
|
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: Unicode Standard | Statement: [Unicode 3.2, addsCharactersTo, Unicode Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsCharactersTo Context triple: [Unicode 3.2, addsCharactersTo, Unicode Standard]
-
A.
providesAdditionalCharactersFor
chosen
Indicates that one entity supplies extra or supplementary characters to be used by another entity or process.
-
B.
addsCharactersCount
Indicates that one entity increases the number of characters (e.g., text length) in another entity by a specified amount.
-
C.
usesCharactersAs
Indicates that one entity employs or incorporates specific characters (such as letters, symbols, or glyphs) from another entity for its representation or functioning.
-
D.
allyOfCharacter
Indicates that one character maintains an alliance or supportive partnership with another character.
-
E.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f2e2df88190948551f6fd67a65a |
completed | May 2, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69f623ac3a9c8190a6ee0c137b09e4b0 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:23 p.m.