Triple
T6288581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Messianic Jews |
E140958
|
entity |
| Predicate | mayObserve |
P70702
|
FINISHED |
| Object | Shabbat on Saturday |
—
|
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: Shabbat on Saturday | Statement: [Messianic Jews, mayObserve, Shabbat on Saturday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayObserve Context triple: [Messianic Jews, mayObserve, Shabbat on Saturday]
-
A.
observedFor
Indicates that one entity is monitored, watched, or examined over a period of time for the benefit or analysis of another entity.
-
B.
mayPresent
Indicates that one entity is permitted or authorized to present, display, or introduce another entity or item.
-
C.
observesFrom
Indicates that one entity watches, monitors, or takes note of another entity from a particular vantage point or location.
-
D.
observedBy
Indicates that an entity is perceived, monitored, or recorded by another entity acting as the observer.
-
E.
notObservedBy
Indicates that an entity, event, or condition is not detected, recorded, or perceived by a specified observer or observation process.
- 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_69c008cd17c8819082b82d3fbeb68047 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064182f60819093a8313e1dbf2763 |
completed | March 22, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69c060df0d8881908215575862ef6831 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c06284848c8190a0151ff3e8682889 |
completed | March 22, 2026, 9:43 p.m. |
Created at: March 22, 2026, 4:26 p.m.