Triple
T37945048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | קו ירוק |
E946581
|
entity |
| Predicate | מסומן לעיתים בשטח באמצעות |
P188782
|
FINISHED |
| Object | גדרות, מחסומים וסימוני גבול נקודתיים |
—
|
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: גדרות, מחסומים וסימוני גבול נקודתיים | Statement: [קו ירוק, מסומן לעיתים בשטח באמצעות, גדרות, מחסומים וסימוני גבול נקודתיים]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: מסומן לעיתים בשטח באמצעות Context triple: [קו ירוק, מסומן לעיתים בשטח באמצעות, גדרות, מחסומים וסימוני גבול נקודתיים]
-
A.
usedAsLocationIn
Indicates that something serves as the setting or place where another event, action, or situation occurs.
-
B.
notableAreaWithin
Indicates that one area is a particularly significant or noteworthy part located inside another, larger area.
-
C.
utilizationArea
Indicates the functional domain, field, or context in which something is used or applied.
-
D.
usedInOrAround
chosen
Indicates that something is utilized, applied, or occurs within the context of, or in the immediate vicinity of, something else.
-
E.
reservePositionArea
Indicates that an area is designated or set aside to hold or reserve a specific position or set of positions.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.