Triple
T158762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | mezuzah |
E3233
|
entity |
| Predicate | isPositioned |
P3250
|
FINISHED |
| Object | upper third of the doorpost |
—
|
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: upper third of the doorpost | Statement: [mezuzah, isPositioned, upper third of the doorpost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPositioned Context triple: [mezuzah, isPositioned, upper third of the doorpost]
-
A.
appliesToPosition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
-
B.
positionOn
chosen
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
isOn
Indicates that one entity is physically positioned above and in contact with the top surface of another entity.
-
D.
locatedAfter
Indicates that one entity is positioned later than another along a defined sequence, order, or spatial/temporal axis.
-
E.
positionHeld
Indicates that an entity occupies or has occupied a specific role, job, office, or position within an organization or context.
- 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.