Triple
T4402286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahad Ha'am Street (Tel Aviv) |
E93644
|
entity |
| Predicate | hasStreetSignType |
P32040
|
FINISHED |
| Object | trilingual street signs |
—
|
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: trilingual street signs | Statement: [Ahad Ha'am Street (Tel Aviv), hasStreetSignType, trilingual street signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetSignType Context triple: [Ahad Ha'am Street (Tel Aviv), hasStreetSignType, trilingual street signs]
-
A.
hasSignageType
chosen
Indicates the specific category or kind of signage associated with an object, location, or entity.
-
B.
hasSignageName
Indicates that an entity has a specific name or label as it appears on its physical signage.
-
C.
hasSignage
Indicates that appropriate signs or visual markers are present to convey information, directions, warnings, or identification related to the associated entity.
-
D.
callSignType
Indicates the classification or category of a call sign associated with an entity or communication.
-
E.
hasTypeOfInsignia
Indicates that an entity bears or is associated with a specific kind or category of insignia.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d08a0c8190ac6c125df40eca75 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.