Triple
T26612157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Be’er Heitev |
E667952
|
entity |
| Predicate | alsoCoversSection |
P41428
|
FINISHED |
| Object | Even HaEzer |
—
|
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: Even HaEzer | Statement: [Be’er Heitev, alsoCoversSection, Even HaEzer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoCoversSection Context triple: [Be’er Heitev, alsoCoversSection, Even HaEzer]
-
A.
alsoCovers
Indicates that something extends its scope or applicability to include an additional subject, area, or case beyond what was originally covered.
-
B.
coversSection
chosen
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
-
C.
section43Covers
Indicates that a specific legal or regulatory section (section 43) applies to, governs, or provides coverage for a particular subject, case, or situation.
-
D.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
E.
isCoveredIn
Indicates that one entity has its surface or area overlaid, coated, or blanketed by another substance or material.
- 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f615aa023c81908858893e8a7067af |
completed | May 2, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:17 a.m.