Triple
T37547457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashkenazi halakha |
E933500
|
entity |
| Predicate | hasCustomsTerm |
P170313
|
FINISHED |
| Object | minhag Ashkenaz |
—
|
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: minhag Ashkenaz | Statement: [Ashkenazi halakha, hasCustomsTerm, minhag Ashkenaz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomsTerm Context triple: [Ashkenazi halakha, hasCustomsTerm, minhag Ashkenaz]
-
A.
hasCustomsReportingRequirement
Indicates that an entity is obligated to report certain activities, goods, or transactions to customs authorities in accordance with applicable regulations.
-
B.
hasSpecialCustomsStatus
Indicates that an entity holds a designated special customs status affecting how it is treated in customs procedures.
-
C.
hasCustomsAgency
Indicates that an entity is associated with or overseen by a specific customs agency responsible for regulating and controlling cross-border goods and related activities.
-
D.
hadCustoms
chosen
Indicates that one entity possessed or maintained particular customs, traditions, or habitual practices associated with another entity or context.
-
E.
supportsCustomsClearance
Indicates that one entity provides or enables customs clearance services or processes for another entity or shipment.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
Created at: May 3, 2026, 4:17 p.m.