Triple
T6173401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maran |
E137758
|
entity |
| Predicate | famousUsageContext |
P58306
|
FINISHED |
| Object | halachic 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: halachic literature | Statement: [Maran, famousUsageContext, halachic literature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousUsageContext Context triple: [Maran, famousUsageContext, halachic literature]
-
A.
isFamouslyUsedBy
Indicates that something is widely and notably used by a particular person, group, or entity, in a way that is broadly recognized or associated with them.
-
B.
isFamouslyUsedIn
chosen
Indicates that something is widely recognized or well-known for being used in a particular context, work, or situation.
-
C.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
-
D.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
E.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
- 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.