Triple
T5533112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sefer HaMadda |
E145095
|
entity |
| Predicate | writtenByRole |
P47055
|
FINISHED |
| Object | medieval Jewish philosopher |
—
|
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: medieval Jewish philosopher | Statement: [Sefer HaMadda, writtenByRole, medieval Jewish philosopher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writtenByRole Context triple: [Sefer HaMadda, writtenByRole, medieval Jewish philosopher]
-
A.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
-
B.
writtenByCulture
Indicates that something (such as a text, work, or artifact) is authored, created, or produced by a particular culture or cultural group.
-
C.
literaryRole
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
D.
hasWritingCreditOn
chosen
Indicates that an entity is credited as a writer or co-writer for a particular work or production.
-
E.
writtenForCharacter
Indicates that a piece of writing (such as a script, scene, or dialogue) was specifically created or tailored for a particular character.
- 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f9ea2c88190a68642f5799bd8ff |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.