Triple
T2024526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Platform |
E44177
|
entity |
| Predicate | viewOfJewishLaw |
P8264
|
FINISHED |
| Object | evolving and adaptable |
—
|
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: evolving and adaptable | Statement: [Pittsburgh Platform, viewOfJewishLaw, evolving and adaptable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOfJewishLaw Context triple: [Pittsburgh Platform, viewOfJewishLaw, evolving and adaptable]
-
A.
viewsHalakhaAs
chosen
Indicates that one entity regards or interprets Halakha (Jewish law) in a particular way, such as considering it authoritative, binding, flexible, or symbolic.
-
B.
judaismView
Indicates a relationship where one entity holds a particular view, interpretation, or doctrinal position within or about Judaism regarding another entity or topic.
-
C.
halachicCategory
Indicates the classification of something according to Jewish legal (halachic) categories or rulings.
-
D.
halakhicApproach
Indicates an entity’s method, stance, or interpretive framework for applying or understanding Jewish law (halakha) in practice.
-
E.
halachicNote
Indicates a relationship where one entity serves as a halachic (Jewish legal) note, comment, or annotation providing legal clarification or guidance about 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f2cd5c8190b19da6f6aa2001d6 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.