Triple
T1113052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maimonides |
E11036
|
entity |
| Predicate | notableWorkOn |
P4941
|
FINISHED |
| Object | Jewish law codification |
—
|
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: Jewish law codification | Statement: [Maimonides, notableWorkOn, Jewish law codification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkOn Context triple: [Maimonides, notableWorkOn, Jewish law codification]
-
A.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
-
B.
notableWorkWrittenThere
Indicates that a notable work was written at or in the specified place.
-
C.
notableWorkContained
Indicates that a notable work is included within or is part of another entity, such as a collection, publication, or compilation.
-
D.
notableWorkSubject
chosen
Indicates that a work is notably associated with a particular subject, such as a person, topic, or entity, as its primary focus or theme.
-
E.
namedForNotableWork
Indicates that one entity is named in honor of another entity’s notable work or achievement.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.