Triple
T6173457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HaMechaber |
E137759
|
entity |
| Predicate | usedAsCitationName |
P4977
|
FINISHED |
| Object | halakhic responsa |
—
|
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: halakhic responsa | Statement: [HaMechaber, usedAsCitationName, halakhic responsa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCitationName Context triple: [HaMechaber, usedAsCitationName, halakhic responsa]
-
A.
usesCitation
Indicates that one entity supports or references its content by citing another entity as a source.
-
B.
citationAs
Indicates that one entity is cited or referenced in the role or capacity specified by another entity (such as a particular work, version, or context).
-
C.
oftenCitedAs
Indicates that one entity is frequently referenced or mentioned as an example, source, or authority in relation to another entity.
-
D.
isCitedWithTaxonName
Indicates that a work, statement, or reference is cited together with a specific taxon name in a taxonomic or scientific context.
-
E.
hasNominativeCitation
chosen
Indicates that an entity is associated with its standard or canonical citation form used as the primary reference.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d94c47481909745b2533926a1ca |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.