Triple
T22361757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish liturgy |
E552794
|
entity |
| Predicate | structuredBy |
P4786
|
FINISHED |
| Object | halakha |
—
|
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: halakha | Statement: [Jewish liturgy, structuredBy, halakha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuredBy Context triple: [Jewish liturgy, structuredBy, halakha]
-
A.
organizedAs
chosen
Indicates how elements are structured, arranged, or grouped according to a particular organizing principle or scheme.
-
B.
organizedFrom
Indicates that something has been arranged, structured, or formed starting from a specified source or initial set of elements.
-
C.
organizedUnder
Indicates that one entity is administratively or structurally placed within, and governed or managed by, another entity.
-
D.
fullyOrganizedBy
Indicates that an event, activity, or process is completely planned, coordinated, and managed by a specified organizing entity.
-
E.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157d44a908190b16e4cfdf4591b10 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.