Triple
T2998614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalet |
E81130
|
entity |
| Predicate | alphabetFamily |
P5793
|
FINISHED |
| Object | Semitic abjads |
—
|
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: Semitic abjads | Statement: [Dalet, alphabetFamily, Semitic abjads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphabetFamily Context triple: [Dalet, alphabetFamily, Semitic abjads]
-
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.
typeFamily
Indicates that one entity is classified as a family-related type or belongs to a family category in relation to another entity.
-
C.
writingSystemFamilyRole
Indicates the role or function that a writing system family plays within a broader linguistic, cultural, or communicative context.
-
D.
scriptFamily
chosen
Indicates that one writing system belongs to the same broader script group or classification as another.
-
E.
familyNameCategory
Indicates that an entity is associated with a particular classification or grouping based on its family name.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f766408190a5591efce8346bb9 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.