Triple
T158747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mezuzah |
E3233
|
entity |
| Predicate | isObservedBy |
P1165
|
FINISHED |
| Object | Jews |
—
|
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: Jews | Statement: [mezuzah, isObservedBy, Jews]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isObservedBy Context triple: [mezuzah, isObservedBy, Jews]
-
A.
observedBy
chosen
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
B.
observerStatusIn
Indicates that an entity’s status or role is defined or valid within a specified observational context, system, or environment.
-
C.
hasObserver
Indicates that an entity is being watched, monitored, or examined by another entity acting as an observer.
-
D.
hasObserverStates
Indicates that an entity is associated with one or more observer-specific states or conditions under which it is perceived or evaluated.
-
E.
observesDay
Indicates that an entity recognizes, commemorates, or practices a particular day (such as a holiday, event, or observance) according to some calendar or tradition.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.