Triple
T34572338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tevul Yom |
E887656
|
entity |
| Predicate | legalStatusTermExplained |
P199562
|
FINISHED |
| Object | tevul yom |
—
|
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: tevul yom | Statement: [Tevul Yom, legalStatusTermExplained, tevul yom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusTermExplained Context triple: [Tevul Yom, legalStatusTermExplained, tevul yom]
-
A.
legalStatusClarifiedBy
Indicates that the legal status of something is defined, explained, or resolved by a specific document, decision, or authoritative act.
-
B.
legalDefinitionCompliance
Indicates that an entity or action conforms to, satisfies, or is consistent with the applicable legal definitions established by laws or regulations.
-
C.
legalTermIn
Indicates that a particular legal term or concept is used, defined, or applicable within a specified legal document, jurisdiction, or context.
-
D.
legalCodeStatus
Indicates the legal or regulatory status assigned to a specific code within a legal or statutory system (e.g., active, repealed, pending).
-
E.
legalTermRefersTo
chosen
Indicates that a specific legal term denotes, references, or is defined by another concept, provision, or entity within a legal 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff691f5ae481908597ce245188d31c |
completed | May 9, 2026, 5:04 p.m. |
| PD | Predicate disambiguation | batch_69ff67ceeeb081909fd00cad166c4b6a |
completed | May 9, 2026, 4:58 p.m. |
Created at: May 1, 2026, 2:03 a.m.