Triple
T37547602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mapah on Shulchan Aruch |
E933503
|
entity |
| Predicate | mainWorkGlossed |
P40956
|
FINISHED |
| Object | Shulchan Aruch |
—
|
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: Shulchan Aruch | Statement: [Mapah on Shulchan Aruch, mainWorkGlossed, Shulchan Aruch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainWorkGlossed Context triple: [Mapah on Shulchan Aruch, mainWorkGlossed, Shulchan Aruch]
-
A.
primaryWork
chosen
Indicates that one work is the main or most significant work associated with a given entity, as opposed to other secondary or related works.
-
B.
mainWorkPeriod
Indicates the primary or most significant span of time during which an entity is active, employed, or engaged in a particular work or role.
-
C.
mainWorkSite
Indicates the primary location or site where an entity mainly performs its work or operations.
-
D.
mainWorkStatus
Indicates the current primary state or condition of a work (such as active, completed, pending, or inactive) within a given process or system.
-
E.
keyWorkOf
Indicates that the subject is a central, defining, or most important work created by the object (such as an artist, author, or creator).
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.