Triple
T35482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten Commandments |
E701
|
entity |
| Predicate | mediumOfOriginalReception |
P166
|
FINISHED |
| Object | stone tablets |
—
|
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: stone tablets | Statement: [Ten Commandments, mediumOfOriginalReception, stone tablets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediumOfOriginalReception Context triple: [Ten Commandments, mediumOfOriginalReception, stone tablets]
-
A.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
B.
fareMedia
Indicates that a particular type of ticket, pass, or payment instrument is used as the medium for paying a fare.
-
C.
theater
Indicates that an entity is a theater or is functioning in the role of a theater (a venue where performances or films are shown).
-
D.
medium
chosen
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
-
E.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24989c3308190af59dfae37cfc32f |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a24873e97c8190b9e4279e43b6de14 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.