Triple
T24857530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleph |
E622066
|
entity |
| Predicate | letterFamily |
P150002
|
FINISHED |
| Object | אחה"ע guttural group |
—
|
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: אחה"ע guttural group | Statement: [Aleph, letterFamily, אחה"ע guttural group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: letterFamily Context triple: [Aleph, letterFamily, אחה"ע guttural group]
-
A.
textualFamily
Indicates that two or more texts are related through a shared origin, tradition, or lineage, forming a recognizable textual group or family.
-
B.
styleFamily
Indicates that one style is grouped within the same stylistic family or category as another style.
-
C.
lineFamily
Indicates that two entities belong to the same family or lineage associated with a particular line (e.g., a family line or line-based grouping).
-
D.
hasLetterforms
chosen
Indicates a relationship where one entity possesses or includes specific letterforms as part of its written or typographic representation.
-
E.
patronFamily
Indicates that one family serves as a patron or protector, providing support or sponsorship to another family.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:21 a.m.