Triple
T31342245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highway 65 (Israel) |
E799335
|
entity |
| Predicate | languageOfOfficialSigns |
P4196
|
FINISHED |
| Object | Hebrew |
—
|
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: Hebrew | Statement: [Highway 65 (Israel), languageOfOfficialSigns, Hebrew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfOfficialSigns Context triple: [Highway 65 (Israel), languageOfOfficialSigns, Hebrew]
-
A.
officialLanguageOfSignage
Indicates that a particular language is the one officially used on public signs and signage within a given place or context.
-
B.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
C.
languageOfSignage
chosen
Indicates the language used on signs or written displays associated with an entity.
-
D.
declaresOfficialLanguageOf
Indicates that an authority formally designates a particular language as the official language of a specified entity or jurisdiction.
-
E.
languageOfSignatures
Indicates the language in which the signatures on a document or agreement are written or expressed.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff76ac40988190a34d858b5472ee2b |
completed | May 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69ff760a90948190a12fcb80e6e3e14b |
completed | May 9, 2026, 5:59 p.m. |
Created at: April 29, 2026, 9:17 p.m.