Triple
T31663213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jewish feminist movement |
E808057
|
entity |
| Predicate | addressesDomain |
P175471
|
FINISHED |
| Object | Halakha |
—
|
NE NERFINISHED |
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 feminist movement, addressesDomain, Halakha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addressesDomain Context triple: [Jewish feminist movement, addressesDomain, Halakha]
-
A.
addressesAuthority
Indicates that one entity directs communication, requests, or appeals to another entity recognized as having authority or decision-making power.
-
B.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
C.
emailAddressDomain
Indicates that one entity is the domain portion (e.g., "example.com") of another entity’s email address.
-
D.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
E.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
- F. None of above. chosen
Provenance (4 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: April 30, 2026, 10:58 p.m.