Triple
T113304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashrut |
E2290
|
entity |
| Predicate | hasCertificationSymbol |
P1617
|
FINISHED |
| Object | hechsher |
—
|
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: hechsher | Statement: [Kashrut, hasCertificationSymbol, hechsher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCertificationSymbol Context triple: [Kashrut, hasCertificationSymbol, hechsher]
-
A.
hasTypeOfInsignia
chosen
Indicates that an entity bears or is associated with a specific kind or category of insignia.
-
B.
qualificationBadge
Indicates that an entity has been awarded or holds a specific qualification badge signifying a certified skill, status, or achievement.
-
C.
certificationDate
Indicates the date on which an entity was officially certified or granted a formal certification.
-
D.
hasLEEDCertification
Indicates that an entity possesses a LEED (Leadership in Energy and Environmental Design) certification, signifying compliance with specified green building and sustainability standards.
-
E.
hasIconicStatus
Indicates that an entity holds a widely recognized, emblematic, or culturally significant status within a particular domain or context.
- 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_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. |
Created at: Feb. 28, 2026, 2:20 a.m.