Triple
T34424446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makkot |
E883630
|
entity |
| Predicate | orderNumberInNezikin |
P181378
|
FINISHED |
| Object | fifth or sixth (depending on tradition) |
—
|
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: fifth or sixth (depending on tradition) | Statement: [Makkot, orderNumberInNezikin, fifth or sixth (depending on tradition)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderNumberInNezikin Context triple: [Makkot, orderNumberInNezikin, fifth or sixth (depending on tradition)]
-
A.
orderNumber
Indicates the unique identifier assigned to a specific order within a transaction or ordering process.
-
B.
orderNumberInSixOrders
chosen
Indicates that an entity has a specific order number or position within a sequence of six orders.
-
C.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
D.
orden
Indicates that one entity issues, gives, or establishes an order, command, or directive concerning another entity or situation.
-
E.
isOrderIn
Indicates that one entity is contained within or belongs to a specified order or sequence of entities.
- 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_69f349c3dd2c819092cc9e64809f4a42 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 2 a.m.