Triple
T13275953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEBREW LETTER FINAL PE |
E316188
|
entity |
| Predicate | UTF8Encoding |
P55911
|
FINISHED |
| Object | 0xD7 0xA3 |
—
|
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: 0xD7 0xA3 | Statement: [HEBREW LETTER FINAL PE, UTF8Encoding, 0xD7 0xA3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UTF8Encoding Context triple: [HEBREW LETTER FINAL PE, UTF8Encoding, 0xD7 0xA3]
-
A.
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.
-
B.
usesCharacterSet
Indicates that one entity employs or relies on a specific character set defined by another entity for encoding or representing text.
-
C.
encodingIndependence
Indicates that a relationship or property holds regardless of the specific encoding or representation used for the involved entities.
-
D.
textEncoderType
chosen
Indicates the specific kind or configuration of encoder used to process or represent text in a system or model.
-
E.
hasUnicodeStandard
Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.