Triple
T13367650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abjad |
E318980
|
entity |
| Predicate | scriptFamilyAssociation |
P5793
|
FINISHED |
| Object | Semitic scripts |
—
|
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 scripts | Statement: [Abjad, scriptFamilyAssociation, Semitic scripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptFamilyAssociation Context triple: [Abjad, scriptFamilyAssociation, Semitic scripts]
-
A.
scriptFamily
chosen
Indicates that one writing system belongs to the same broader script group or classification as another.
-
B.
scriptFamilyStatus
Indicates the familial or relational status between scripts, such as whether one script is derived from, related to, or grouped with another within a script family.
-
C.
familyAlliance
Indicates a cooperative or supportive relationship formed between families, often involving mutual obligations, shared interests, or joint actions.
-
D.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
-
E.
gangAffiliationThroughFamily
Indicates that an individual is affiliated with a gang due to family connections or relationships.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadcd652d48190a782fd1f57f34b6a |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.