Triple
T112716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judeo-Arabic |
E2282
|
entity |
| Predicate | hasLinguisticElement |
P7161
|
FINISHED |
| Object | Hebrew vocabulary |
—
|
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: Hebrew vocabulary | Statement: [Judeo-Arabic, hasLinguisticElement, Hebrew vocabulary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLinguisticElement Context triple: [Judeo-Arabic, hasLinguisticElement, Hebrew vocabulary]
-
A.
hasSignificantLanguage
Indicates that an entity possesses a language that plays an important or primary role in its communication, identity, or functioning.
-
B.
hasProtoLanguage
Indicates that a language or language family originates from, or is derived from, a specified proto-language.
-
C.
hasLanguageGroup
Indicates that an entity belongs to, is associated with, or is categorized under a particular language group.
-
D.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
E.
hasCognate
Indicates that two linguistic forms in different languages share a common historical origin, typically descending from the same ancestral word.
- F. None of above. chosen
Provenance (4 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a256425a488190959d71e39e699d90 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2587e598c81909e1082b813971f48 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.