Triple
T19864292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daʻat |
E477346
|
entity |
| Predicate | countingConvention |
P99808
|
FINISHED |
| Object | sometimesExcludedFromTenSefirot |
—
|
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: sometimesExcludedFromTenSefirot | Statement: [Daʻat, countingConvention, sometimesExcludedFromTenSefirot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countingConvention Context triple: [Daʻat, countingConvention, sometimesExcludedFromTenSefirot]
-
A.
alternativeCounting
chosen
Indicates that there exists another valid way of counting or enumerating the same set of items or events, distinct from the primary counting method.
-
B.
countingRule
Indicates the rule or method used to count or quantify items, events, or entities in a given context.
-
C.
followsCountingSystemOf
Indicates that one entity uses or adheres to the same counting or numeral system as another entity.
-
D.
areCountedBy
Indicates that one entity serves as the counting mechanism, record, or process by which the quantity of another entity is determined.
-
E.
numberOfCounts
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
- 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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6589d55a88190af7d4e12c4b07739 |
completed | April 20, 2026, 4:47 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.