Triple
T11146883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ha-Kadosh |
E263690
|
entity |
| Predicate | grammaticalArticle |
P7764
|
FINISHED |
| Object | ha- |
—
|
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: ha- | Statement: [ha-Kadosh, grammaticalArticle, ha-]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grammaticalArticle Context triple: [ha-Kadosh, grammaticalArticle, ha-]
-
A.
grammaticalType
Indicates the grammatical category or role (such as part of speech or syntactic function) that an expression has within a language.
-
B.
grammaticalForm
chosen
Indicates the specific grammatical structure or morphological form that an expression or word takes in a given linguistic context.
-
C.
grammaticalDescription
Indicates that one entity provides a description or explanation of the grammatical properties or structure of another entity.
-
D.
grammaticalAlignment
Indicates how a language aligns core grammatical roles (such as subject, object, or agent, patient) in its case marking or agreement system.
-
E.
grammaticalStructure
Indicates the way linguistic elements are organized and related within a sentence or phrase according to grammatical rules.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.