Triple
T4471902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Sayer of the Law |
E98512
|
entity |
| Predicate | recites |
P56737
|
FINISHED |
| Object | the Law |
—
|
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: the Law | Statement: [the Sayer of the Law, recites, the Law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recites Context triple: [the Sayer of the Law, recites, the Law]
-
A.
recitedOnOccasion
Indicates that something (typically a text, speech, or performance) was recited during or in connection with a specific occasion or event.
-
B.
recurs
Indicates that an event, condition, or pattern happens again, often repeatedly or at regular intervals, after having occurred before.
-
C.
recitationTradition
Indicates a relationship where a text, work, or content is transmitted or performed according to a particular established style, method, or lineage of recitation.
-
D.
reiterates
Indicates that an entity repeats or restates something that was previously expressed, often to emphasize or clarify it.
-
E.
recitationCustom
Indicates that one entity performs or delivers a recitation in a customized or non-standard manner for another entity or context.
- 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
| PDg | Predicate description generation | batch_69b356f9afc48190acb50c45a310e072 |
completed | March 13, 2026, 12:14 a.m. |
Created at: March 12, 2026, 11:35 p.m.