Triple
T13275933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEBREW LETTER FINAL PE |
E316188
|
entity |
| Predicate | ISO10646Comment |
P109284
|
FINISHED |
| Object | final form of pe |
—
|
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: final form of pe | Statement: [HEBREW LETTER FINAL PE, ISO10646Comment, final form of pe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO10646Comment Context triple: [HEBREW LETTER FINAL PE, ISO10646Comment, final form of pe]
-
A.
ISO15924Status
Indicates the official status or classification of a script according to the ISO 15924 standard.
-
B.
ISOBasicLatinDerivative
Indicates that one entity is a derivative or variant form of another entity within the ISO Basic Latin character set.
-
C.
hasUnicodeStandard
Indicates that something conforms to, is defined by, or is associated with a particular version or aspect of the Unicode standard.
-
D.
UnicodeStandardVersionIntroduced
Indicates the specific version of the Unicode Standard in which a given character, feature, or property was first introduced.
-
E.
codingSystemType
Indicates the classification or category of coding system used to encode or represent information in a given context.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:26 p.m.