Triple
T37945046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | קו ירוק |
E946581
|
entity |
| Predicate | לא הוכר רשמית כ |
P155420
|
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.
notOfficialIn
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or jurisdiction.
-
B.
notOfficiallyProclaimedBy
chosen
Indicates that something has not been formally or legally announced, declared, or recognized by the specified authority or entity.
-
C.
hasNoOfficialRecordIn
Indicates that an entity lacks any recognized or formally documented record within a specified system, registry, or authority.
-
D.
notSignedAs
Indicates that an entity is explicitly not using, associated with, or represented under a specified name, signature, or identity.
-
E.
notOfficialNameOf
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
- 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.