Triple
T9052068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unicode 3.0 |
E216905
|
entity |
| Predicate | definesEncodingForm |
P66343
|
FINISHED |
| Object | UTF-8 |
—
|
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: UTF-8 | Statement: [Unicode 3.0, definesEncodingForm, UTF-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesEncodingForm Context triple: [Unicode 3.0, definesEncodingForm, UTF-8]
-
A.
encodingForm
chosen
Indicates the specific format or scheme used to encode information or data in a representation or communication.
-
B.
dataEncodingMethod
Indicates the specific technique or format used to encode data for storage, transmission, or processing.
-
C.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
D.
requestEncoding
Indicates that one entity asks another to use or provide a specific encoding format for data or communication.
-
E.
definesFormatFor
Indicates that one entity specifies or establishes the format or structural pattern to be used by another entity.
- 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.