Triple
T36761280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbeinu haKadosh |
E908205
|
entity |
| Predicate | honorificUsedBy |
P42968
|
FINISHED |
| Object | later rabbinic literature |
—
|
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: later rabbinic literature | Statement: [Rabbeinu haKadosh, honorificUsedBy, later rabbinic literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificUsedBy Context triple: [Rabbeinu haKadosh, honorificUsedBy, later rabbinic literature]
-
A.
honorificUse
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
B.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
C.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
D.
honorificContext
Indicates that one entity is referred to or addressed using an honorific form or within a socially respectful linguistic context relative to another entity or situation.
-
E.
honorificIndicates
chosen
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
- 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_69f76e779bec8190be0e1f87a131e0f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:12 p.m.