Triple
T1239548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te'amim |
E26626
|
entity |
| Predicate | includeCategory |
P15481
|
FINISHED |
| Object | disjunctive accents |
—
|
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: disjunctive accents | Statement: [Te'amim, includeCategory, disjunctive accents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeCategory Context triple: [Te'amim, includeCategory, disjunctive accents]
-
A.
category
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
B.
commonsCategory
Indicates that an entity is associated with a specific media or topic category on Wikimedia Commons.
-
C.
hasCategoryOn
chosen
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
D.
uniformCategory
Indicates that two or more entities share the same classification or type within a defined category system.
-
E.
settingCategory
Indicates the classification or type of context in which something is set or configured (e.g., grouping settings under a common category).
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf41c5d08190b07adbdb24d35a76 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb67d52c8190815d6356b79d6ed5 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.