Triple
T36374676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moed Katan |
E895866
|
entity |
| Predicate | alsoDiscusses |
P33880
|
FINISHED |
| Object | laws of mourning |
—
|
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: laws of mourning | Statement: [Moed Katan, alsoDiscusses, laws of mourning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoDiscusses Context triple: [Moed Katan, alsoDiscusses, laws of mourning]
-
A.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
-
B.
discussed
Indicates that one entity talked about, examined, or debated a topic, issue, or other entity with someone else.
-
C.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
D.
containsDiscussionOf
chosen
Indicates that one entity includes or features a discussion, treatment, or consideration of another entity as a topic or subject.
-
E.
alsoConsidered
Indicates that one item is regarded as an alternative or additional option alongside another in a given context.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.