Triple
T32654517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torah ark |
E834824
|
entity |
| Predicate | oftenInscribedWith |
P54400
|
FINISHED |
| Object | Ten Commandments |
—
|
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: Ten Commandments | Statement: [Torah ark, oftenInscribedWith, Ten Commandments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenInscribedWith Context triple: [Torah ark, oftenInscribedWith, Ten Commandments]
-
A.
commonlyInscribedIn
Indicates that something is typically written, carved, or engraved onto a particular surface, object, or medium.
-
B.
oftenDepictedWithInscription
Indicates that the subject is frequently shown or represented together with a written inscription.
-
C.
mayBeInscribedOn
Indicates that one entity is permitted or suitable to be written, engraved, or otherwise inscribed on another entity.
-
D.
inscribedTogetherWith
chosen
Indicates that one entity is inscribed jointly with another on the same surface, object, or document as part of a single inscription context.
-
E.
isInscribedOn
Indicates that text, symbols, or markings are written, carved, or otherwise permanently placed onto the surface of an object.
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:08 a.m.