Triple
T13275949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEBREW LETTER FINAL PE |
E316188
|
entity |
| Predicate | hasGlyphVariant |
P455
|
FINISHED |
| Object | sofit 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: sofit form of Pe | Statement: [HEBREW LETTER FINAL PE, hasGlyphVariant, sofit form of Pe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlyphVariant Context triple: [HEBREW LETTER FINAL PE, hasGlyphVariant, sofit form of Pe]
-
A.
hasGlyphsFor
Indicates that one entity provides or contains the necessary glyphs or visual symbols to represent another entity.
-
B.
hasVariant
chosen
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
C.
hasVariantText
Indicates that an entity is associated with an alternative or differing textual form of its content.
-
D.
hasGlyphRepertoireSize
Indicates the number of distinct glyphs included in an entity’s glyph repertoire.
-
E.
hasLigatures
Indicates that one writing system, font, or text includes combined character forms (ligatures) that join two or more individual glyphs into a single symbol.
- 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.